Files
everything-claude-code/agents/conversation-analyzer.md
Affaan Mustafa 4813ed753f 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
2026-03-31 21:55:43 -07:00

52 lines
1.4 KiB
Markdown

---
name: conversation-analyzer
description: Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /hookify without arguments.
model: sonnet
tools: [Read, Grep]
---
# Conversation Analyzer Agent
You analyze conversation history to identify problematic Claude Code behaviors that should be prevented with hooks.
## What to Look For
### Explicit Corrections
- "No, don't do that"
- "Stop doing X"
- "I said NOT to..."
- "That's wrong, use Y instead"
### Frustrated Reactions
- User reverting changes Claude made
- Repeated "no" or "wrong" responses
- User manually fixing Claude's output
- Escalating frustration in tone
### Repeated Issues
- Same mistake appearing multiple times in the conversation
- Claude repeatedly using a tool in an undesired way
- Patterns of behavior the user keeps correcting
### Reverted Changes
- `git checkout -- file` or `git restore file` after Claude's edit
- User undoing or reverting Claude's work
- Re-editing files Claude just edited
## Output Format
For each identified behavior:
```yaml
behavior: "Description of what Claude did wrong"
frequency: "How often it occurred"
severity: high|medium|low
suggested_rule:
name: "descriptive-rule-name"
event: bash|file|stop|prompt
pattern: "regex pattern to match"
action: block|warn
message: "What to show when triggered"
```
Prioritize high-frequency, high-severity behaviors first.