skills.rest
Jennyfirrr
JennyfirrrCOMMUNITY
Explore all skills by this author →
GitHub

bug-check

Scan codebases for known bug classes and report per-class verdicts with citations.

Updated Aug 27, 2026
Search Tags:#code-quality#anti-pattern#triage#report#scan#ledger#bug-check
One-click install
npx skills add https://github.com/Jennyfirrr/workspace-template --skill bug-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-check
Source: https://github.com/Jennyfirrr/workspace-template/tree/main/claude-skills/bug-check
Command: npx skills add https://github.com/Jennyfirrr/workspace-template --skill bug-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scan the codebase for recurring bug patterns catalogued in the project's anti-pattern registry, producing structured findings for operator triage.

Core Features & Use Cases

  • Registry-driven audit that reads the anti-pattern catalog and reports per-class status (CLEAN, KNOWN-N, NEW-N) with file:line citations
  • Plan-aware reporting that references associated debt ledgers and downstream decisions for easy triage
  • Output is a non-destructive findings report suitable for review and remediation planning

Quick Start

Run the /bug-check command to generate a current-scope report across the repository.

Frequently Asked Questions about bug-check

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

FAQPage Schema
How do I scan my codebase for recurring anti-patterns and known bug classes?▼

To scan for recurring anti-patterns, run a bug check that reads the project's anti-pattern catalog and reports per-class status with file:line citations. It identifies occurrences of known bug classes across recent edits or broad codebase sweeps.

What is the best way to triage code quality issues using a registry-driven audit?▼

A registry-driven audit triages code quality by scanning against a catalogued anti-pattern registry, producing a structured findings report with verdicts like CLEAN, KNOWN-N, or NEW-N. This output references debt ledgers for easy downstream remediation planning.

Can I generate a structured bug report for module-level codebase sweeps?▼

Yes, you can generate a structured bug report for module-level codebase sweeps. The scan applies to wide-range analyses and outputs a non-destructive findings report containing per-class verdicts and specific file:line citations for operator review.

Does bug checking require an anti-pattern catalog to detect code issues?▼

Yes, bug checking requires an anti-pattern catalog and related docs to detect code issues. The scan relies on this registry input to identify and report occurrences of known bug classes, outputting structured findings with per-class verdicts and citations.

How do code scans handle known bug classes versus newly introduced anti-patterns?▼

Code scans differentiate known bug classes from newly introduced anti-patterns by reporting per-class status as CLEAN, KNOWN-N, or NEW-N. This registry-driven approach outputs structured findings with citations to guide targeted remediation and triage.

Related Skills

Explore More Software Engineering Skills→
vuminhieuvuminhieu

web-design-guidelines

Audit UI code against Web Interface Guidelines and report file:line findings.

Community
Intermediate
tomascuprtomascupr
68

refire

Apply verified code review findings to git repository files and verify fixes.

Community
Advanced
brainbrewlabsbrainbrewlabs
7

code-fixing

Fix code scanner, security auditor, and linter issues with verified edits and reports.

Official
Intermediate
prof-danielcprof-danielc

speckit.checker

Run static analysis tools and aggregate results into a prioritized issue report.

Community
Advanced