Agent skill · Security

audit-bugs

Analyze historical bug patterns by mining Claude Code project logs for /autoskillit: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".

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill audit-bugs --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/analysis/audit-bugs/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Bug Pattern Audit Skill Mine Claude Code conversation logs for `/autoskillit: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

What's inside
Steps it walks through
  1. When to Use
  2. Arguments
  3. Critical Constraints
  4. Workflow
  5. Step 1: Locate Project Logs
  6. Step 2: Filter by Date and Investigate Skill
  7. Step 3: Dispatch Subagents for Parallel Analysis
  8. Step 4: Synthesize Patterns
  9. Step 5: Write Report
  10. Step 6: Terminal Summary
Ships with 1 file
  • metadata.json
Commands it runs
Convert current working directory to Claude's folder naming scheme
Remove leading double dash if present
More from claude-skill-registry
All skills →
About this skill
What does the audit-bugs skill do?

Analyze historical bug patterns by mining Claude Code project logs for /autoskillit: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 --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.

Keep going