Diagnose build, runtime, and database errors in taw-kit projects.
npx skills add https://github.com/nghiahsgs/taw-kit --skill debug-nghiahsgs
Please help me install this Agent Skill. Skill: debug Source: https://github.com/nghiahsgs/taw-kit/tree/main/skills/debug Command: npx skills add https://github.com/nghiahsgs/taw-kit --skill debug-nghiahsgs
Diagnoses and analyzes build, runtime, and database-related errors in taw-kit projects using a structured read-grep-hypothesize-fix loop, enabling faster root-cause identification.
Run taw-fix with the captured error output and follow the guided fix workflow.
High-intent search queries and answers about installing and using this skill.
Diagnosing runtime errors in taw-kit projects involves using a structured read-grep-hypothesize-fix loop. The Skill scopes errors to specific files and lines, reads failing code, greps for related usages, and generates targeted root-cause hypotheses for faster resolution.
Finding the root-cause of build failures is best achieved through hypothesis-driven reasoning. The Skill enforces sequential-thinking for multi-cause failures and proposes concrete fixes that you can verify by running build or dev server tests.
Fixing database-related errors using a structured debugging workflow requires reading the failing code around the error location, grepping for related usages, and generating targeted root-cause hypotheses. It then provides guided fixes and verification steps to validate the changes.
Yes, you need to capture error context before diagnosing build failures. Structured error context capture from builds and dev servers is required to scope errors to specific files and lines, enabling targeted root-cause analysis and guided fixes.
You can verify proposed fixes for multi-cause failures by running build or dev server tests. The debugging process proposes concrete fixes and provides verification steps to validate that the applied changes successfully resolve the detected errors.
0xHarbsDiagnose failures by applying hypothesis-driven root-cause analysis to test outputs, stack traces, and CI logs.
dotnetGuide hypothesis-driven debugging of F# compiler failures with minimal reproductions.
lbrutonRun Codacy static code quality analysis with sequential thinking.
dangelesGuide phase-driven debugging from symptom capture to documented fixes.
