Diagnose software bugs through structured reproduction and falsifiable assertions.
npx skills add https://github.com/n0rvyn/indie-toolkit --skill fix-bug-n0rvyn
Please help me install this Agent Skill. Skill: fix-bug Source: https://github.com/n0rvyn/indie-toolkit/tree/main/dev-workflow/skills/fix-bug Command: npx skills add https://github.com/n0rvyn/indie-toolkit --skill fix-bug-n0rvyn
This Skill guides engineers and maintainers through a structured, evidence-driven bug investigation when users report errors, stack traces, screenshots, or build/test failures, ensuring the root cause is found before code changes are made.
Use the fix-bug skill to investigate the provided error or stack trace, reproduce the issue, generate falsifiable hypotheses with evidence, and produce a user-approved fix plan.
High-intent search queries and answers about installing and using this skill.
To diagnose a software bug from a stack trace, perform structured reproduction to confirm the issue, generate falsifiable hypotheses with file:line evidence, and verify each assertion systematically before planning code changes.
The best way to reproduce a failing CI build locally is to record exact steps that trigger the bug, apply hypothesis-driven assertions, and perform value-domain tracing to pinpoint the root cause before attempting any fixes.
Hypothesis testing for bug fixing prevents accidental regressions by generating 3-5 specific falsifiable assertions with file:line evidence, verifying issues systematically, and gating implementation on explicit approval rather than patching blindly.
Tracing data-related bugs using value-domain analysis involves mapping how data flows through parallel processing paths, ensuring you inspect all related branches to avoid partial fixes and confirm the full scope of the issue.
Yes, you can use this approach for GitHub-linked issues and incident reports where reproduction, hypothesis-driven assertions, and value-domain tracing are required to generate consumer-impact aware repair plans for reliable fixes.
Hypothesis-driven bug diagnosis requires verifiable file:line evidence and structured reproduction, meaning it is limited when issues cannot be consistently reproduced or lack sufficient error context like stack traces and failing build logs.
openyakDiagnose software issues through a structured debugging workflow from reproduction to remediation.
afel6Write failing tests before production code and run test suites to prevent regressions.
shiroinockCoordinate TDD task orchestration from GitHub issue selection to PR completion.
CANTAGESTUDIODiagnose software defects through a four-phase root-cause investigation framework.
