skills.rest
Trecek
TrecekCOMMUNITY
Explore all skills by this author →
GitHub

audit-bugs

Produces audit reports of recurring bug patterns from dated session archives.

1|Updated Feb 14, 2026
Search Tags:#logs#audit#bugs#root-cause#bug-patterns#investigations#proactive-detection
One-click install
npx skills add https://github.com/Trecek/useful-claude-skills --skill audit-bugs-trecek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-bugs
Source: https://github.com/Trecek/useful-claude-skills/tree/main/.claude/skills/audit-bugs
Command: npx skills add https://github.com/Trecek/useful-claude-skills --skill audit-bugs-trecek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze historical bug patterns by mining Claude Code project logs for /investigate invocations since a specified date to surface recurring root causes and architectural gaps.

Core Features & Use Cases

  • Mine Claude Code conversation logs for /investigate invocations to extract recurring bug patterns, root causes, and architectural gaps.
  • Filter investigations by a since date and other criteria to focus on relevant sessions.
  • Produce a structured, timestamped bug-pattern report saved under temp/audit-bugs/bug_pattern_audit_<timestamp>.md.
  • Provide proactive recommendations to close architectural gaps and improve detection across future investigations.

Quick Start

Provide a since date and run the audit to generate a bug-pattern report covering sessions since that date.

Frequently Asked Questions about audit-bugs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify recurring bug patterns from historical Claude Code investigation logs?▼

To identify recurring bug patterns, parse historical Claude Code conversation logs for /investigate invocations and extract root causes alongside architectural gaps to reveal repeating issues across sessions.

How do I audit past bug investigations filtered by a specific start date?▼

Audit past bug investigations by providing a since date to filter historical Claude Code sessions, mine logs for /investigate entries, and generate a timestamped bug-pattern report saved under temp/audit-bugs.

What is the best way to analyze root causes from previous debugging sessions?▼

Analyzing root causes from previous debugging sessions involves mining conversation logs for /investigate invocations using parallel subagents to extract findings, affected components, and suggested preventive actions into a structured report.

Can I extract recurring architectural gaps from Claude Code logs to improve proactive detection?▼

Yes, extracting recurring architectural gaps from Claude Code logs surfaces systemic issues and generates proactive recommendations to close those gaps and improve detection across future investigations.

Where does the bug pattern audit report get saved after analyzing conversation logs?▼

The bug pattern audit report is saved as a structured markdown file with a timestamped filename at temp/audit-bugs/bug_pattern_audit_<timestamp>.md after the log analysis completes.

Do I need any external dependencies to run a bug pattern audit on Claude Code sessions?▼

No external dependencies are required; the audit relies on existing Claude Code conversation logs and uses parallel subagents internally to parse /investigate invocations and compile the final report.

Related Skills

Explore More Software Engineering Skills→
TalonT-OrgTalonT-Org
5

audit-bugs

Mine project logs to identify recurring bug patterns and root causes.

Official
Advanced
TrecekTrecek
1

design-guards

Parse bug pattern audit reports and design architectural guards with tests and contracts.

Community
Advanced
vessuxvessux
1

systematic-debugging

Enforce root-cause investigation before proposing fixes in a four-phase debugging workflow.

Community
Advanced
itsmarsssitsmarsss
4

codex-history-ingest

Mine Codex CLI session logs into structured Obsidian wiki pages.

Community
Advanced