bugReport

Name: bugReport
Availability: InStock
Author: joi-fairshare

Run typecheck, lint, and test suites to produce structured bug reports with health metrics.

1|2|Updated Mar 19, 2026

Search Tags:#testing #linting #triage #read-only #code-audit #bug-report #health-metrics

Ready to run

npx skills add https://github.com/joi-fairshare/agentic-workflow --skill bugreport-joi-fairshare

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bugReport
Source: https://github.com/joi-fairshare/agentic-workflow/tree/main/skills/bugReport
Command: npx skills add https://github.com/joi-fairshare/agentic-workflow --skill bugreport-joi-fairshare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill captures the current state of code health without making any changes, letting you generate structured diagnostic reports for triage and prioritization.

Core Features & Use Cases

Read-only diagnostics: Runs the configured typecheck, lint, and test suites even when issues exist, ensuring no source code or tests are modified.
Structured reporting: Aggregates tool outputs into categorized findings (bugs, tech debt, test gaps, false positives) and computes health scores for testing, typing, and linting.
Use case: Use it to assess a troubled module before dedicating engineering time, surface severity-ranked issues, and provide guidance for /bugHunt or other repair workflows.

Quick Start

Run /bugReport to capture audit details and health metrics for the codebase without altering any files.

Frequently Asked Questions about bugReport

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

FAQPage Schema

How do I generate a bug report for my codebase without modifying source files?▼

You can generate a read-only bug report by running configured typecheck, lint, and test suites without altering source files. This process produces structured diagnostic findings and computes health metrics for testing, typing, and linting to capture current code health.

What is codebase triage and how do health metrics help prioritize modules?▼

Codebase triage involves auditing failure-prone modules to categorize findings into bugs, tech debt, and test gaps. Health metrics score testing, typing, and linting states, helping you assess troubled modules and prioritize engineering efforts before making repairs.

Can I run linting and typecheck suites on a codebase that already has existing errors?▼

Yes, you can execute typecheck, lint, and test suites even when issues exist. The diagnostic process runs in a read-only mode, ensuring no source code or tests are modified while aggregating tool outputs into categorized findings.

What's the best way to surface severity-ranked issues before starting a bug hunt?▼

The best way to surface severity-ranked issues is to run a read-only code audit that aggregates defects, debts, and gaps. This generates structured reports with health metrics, providing necessary guidance for subsequent bug hunt workflows.

Does a read-only code audit separate false positives from actual bugs and tech debt?▼

Yes, a read-only code audit separates false positives from actual bugs and tech debt. It aggregates tool outputs into categorized findings, ensuring your structured diagnostic reports accurately reflect the codebase's true defects and test gaps.