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

agents/pr-test-analyzer.md

@@ -0,0 +1,43 @@
+---
+name: pr-test-analyzer
+description: Use this agent when reviewing a pull request for test coverage quality and completeness. Invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases.
+model: sonnet
+tools: [Read, Grep, Glob, Bash]
+---
+
+# PR Test Analyzer Agent
+
+You review test coverage quality and completeness for pull requests.
+
+## Analysis Process
+
+### 1. Identify Changed Code
+- Parse the PR diff to find new/modified functions, classes, and modules
+- Map changed code to existing test files
+- Identify untested new code paths
+
+### 2. Behavioral Coverage Analysis
+- Check that each new feature has corresponding test cases
+- Verify edge cases are covered (null, empty, boundary values, error states)
+- Ensure error handling paths are tested
+- Check that integration points have integration tests
+
+### 3. Test Quality Assessment
+- Verify tests actually assert meaningful behavior (not just "no throw")
+- Check for proper test isolation (no shared mutable state)
+- Ensure test descriptions accurately describe what's being tested
+- Look for flaky test patterns (timing, ordering, external dependencies)
+
+### 4. Coverage Gap Identification
+Rate each gap by impact (1-10) focused on preventing real bugs:
+- **Critical gaps (8-10)**: Core business logic, security paths, data integrity
+- **Important gaps (5-7)**: Error handling, edge cases, integration boundaries
+- **Nice-to-have (1-4)**: UI variations, logging, non-critical paths
+
+## Output Format
+
+Provide a structured report:
+1. **Coverage Summary**: What's tested vs what's not
+2. **Critical Gaps**: Must-fix before merge
+3. **Improvement Suggestions**: Would strengthen confidence
+4. **Positive Observations**: Well-tested areas worth noting