feat: consolidate all Anthropic plugins into ECC v2.0.0

Ports functionality from 10+ separate plugins into ECC so users only
need one plugin installed. Consolidates: pr-review-toolkit, feature-dev,
commit-commands, hookify, code-simplifier, security-guidance,
frontend-design, explanatory-output-style, and personal skills.

New agents (8): code-architect, code-explorer, code-simplifier,
comment-analyzer, conversation-analyzer, pr-test-analyzer,
silent-failure-hunter, type-design-analyzer

New commands (9): commit, commit-push-pr, clean-gone, review-pr,
feature-dev, hookify, hookify-list, hookify-configure, hookify-help

New skills (8): frontend-design, hookify-rules, github-ops,
knowledge-ops, lead-intelligence, oura-health, pmx-guidelines, remotion

Enhanced skills (8): article-writing, content-engine, market-research,
investor-materials, investor-outreach, x-api, security-scan,
autonomous-loops — merged with personal skill content

New hook: security-reminder.py (pattern-based OWASP vulnerability
warnings on file edits)

Totals: 36 agents, 69 commands, 128 skills, 29 hook scripts
This commit is contained in:
Affaan Mustafa
2026-03-31 21:54:03 -07:00
parent 19755f6c52
commit 4813ed753f
73 changed files with 5618 additions and 27 deletions

28
commands/commit.md Normal file
View File

@@ -0,0 +1,28 @@
---
description: Create a git commit
---
Create a single git commit from staged and unstaged changes with an appropriate message.
## Steps
1. Run `git status` (never use `-uall` flag) and `git diff` in parallel to see all changes
2. Run `git log --oneline -5` to match commit message style
3. Analyze changes and draft a concise commit message following conventional commits format: `<type>: <description>`
- Types: feat, fix, refactor, docs, test, chore, perf, ci
- Focus on "why" not "what"
4. Stage relevant files (prefer specific files over `git add -A`)
5. Create the commit using a HEREDOC for the message:
```bash
git commit -m "$(cat <<'EOF'
type: description
EOF
)"
```
6. Run `git status` to verify success
**Rules:**
- Never skip hooks (--no-verify) or bypass signing
- Never amend existing commits unless explicitly asked
- Do not commit files that likely contain secrets (.env, credentials.json)
- If pre-commit hook fails, fix the issue and create a NEW commit