audit-bugs
Analyze historical bug patterns by mining Claude Code project logs for /investigate skill invocations since a specified date. Identifies recurring root causes, architectural gaps, and proactive detection strategies. Use when user says "audit bugs", "bug patterns", "analyze investigations", or "bug audit".
npx skills add majiayu000/claude-skill-registry --skill audit-bugs-talont-org-autoskillit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Bug Pattern Audit Skill Mine Claude Code conversation logs for `/investigate` skill invocations to identify recurring bug patterns, architectural gaps, and proactive detection strategies. ## When to Use - User says "audit bugs", "bug patterns", "analyze investigations", or "bug audit" - User wants to find recurring themes across past bug investigations - User wants proactive strategies to catch bugs before they manifest ## Arguments The user may provide a "since" date (e.g., `2/7`, `2026-02-07`, `last week`). If not specified, use `AskUserQuestion` to ask what the earliest lookback date should be before proceeding. ## Critical Constraints **NEVER:** - Modify any source code files - Create files outside `temp/audit-bugs/` directory **ALWAYS:** - Use subagents heavily for parallel log analysis - All output goes under `temp/audit-bugs/` (create if needed) - Final report: `temp/audit-bugs/bug_pattern_audit_{YYYY-MM-DD_HHMMSS}.md` - Subagents must NOT create their own files - they return findings in their response text only - Do not change any code ## Workflow ### Step 1: Locate Project Logs Claude Code stores conversation logs at `~/.claude/projects/` in a folder derived from the pro
- When to Use
- Arguments
- Critical Constraints
- Workflow
- Step 1: Locate Project Logs
- Step 2: Filter by Date and Investigate Skill
- Step 3: Dispatch Subagents for Parallel Analysis
- Step 4: Synthesize Patterns
- Step 5: Write Report
- Step 6: Terminal Summary
Convert current working directory to Claude's folder naming scheme Remove leading double dash if present
What does the audit-bugs skill do?
Analyze historical bug patterns by mining Claude Code project logs for /investigate skill invocations since a specified date. Identifies recurring root causes, architectural gaps, and proactive detection strategies. Use when user says "audit bugs", "bug patterns", "analyze investigations", or "bug audit".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill audit-bugs-talont-org-autoskillit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.