code-bug-investigation

Investigate reported defects to confirm root cause and propose a focused regression verification strategy.

138|5|Updated Sep 19, 2024
One-click install
npx skills add https://github.com/macalbert/envilder --skill code-bug-investigation-macalbert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-bug-investigation
Source: https://github.com/macalbert/envilder/tree/main/.github/skills/code-bug-investigation
Command: npx skills add https://github.com/macalbert/envilder --skill code-bug-investigation-macalbert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bug reports often arrive with vague symptoms and no confirmed root cause, leading to premature fixes, redundant tests, and regressions that slip through existing coverage. This Skill turns a defect report into a structured root-cause analysis with reproduction evidence and a ready-to-establish verification plan, without editing any code. ## Core Features & Use Cases - Reproduction-First Investigation: Builds the fastest feedback loop to reproduce the defect before any fix is proposed, and stops with a clear report when reproduction is impossible. - Root Cause Confirmation: Traces the exact code path and condition producing the wrong behavior, separates confirmed observations from assumptions, and identifies invariants the fix must preserve. - Focused Verification Strategy: Recommends reusing, updating, or adding one focused regression at the lowest appropriate test level, with distinct handling for production defects versus test-infrastructure defects. - Use Case: A GitHub issue reports that a CLI flag is ignored. The Skill gathers the issue evidence, reproduces the failure with the narrowest command, confirms the root cause in the dispatch layer, and outputs a BugAnalysis recommending one integration-level regression. ## Quick Start Ask the AI to investigate the bug described in a GitHub issue or user report and produce a BugAnalysis with confirmed root cause and a proposed regression strategy.

Frequently Asked Questions about code-bug-investigation

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

FAQPage Schema
How do I investigate a bug report before writing a fix?

Restate the observed and expected behavior, find the narrowest way to reproduce the symptom, and confirm the root cause with that reproduction before proposing any change. This Skill structures that process and outputs a BugAnalysis with a verification plan.

What test level should a regression test target for a bug?

Choose the lowest level that crosses the failing boundary: unit tests for pure domain rules, integration tests for adapters, DI, or CLI contracts, and e2e tests for critical user journeys. Avoid mocking away the cause of the defect.

Does this Skill fix the bug or modify code?

No. It only investigates and produces a root-cause analysis plus a proposed verification strategy. It never edits production code, tests, documentation, or configuration during investigation.

What happens when a bug cannot be reproduced?

The investigation stops and reports the missing conditions or evidence with a NOT_REPRODUCED status. It surfaces the inability to reproduce instead of guessing at a cause or proposing an unverified fix.

How are test-infrastructure defects handled differently from production bugs?

Test-infrastructure defects start with a consumer test or direct reproduction of the affected workflow rather than the defect-boundary table. Direct tests of shared support code are recommended only when consumer evidence cannot localize the fault.