debug · task skill
Find and repair the cause
Investigate the failure with evidence instead of repeated guesses.
bring
Expected and observed behavior, a trigger, relevant code and safe logs.
your agent does
Reproduce where possible, test competing causes, repair and check for regression.
you get
A diagnosis, repair evidence and any unresolved uncertainty.
ask in your agent’s chat
Use FDEOps debug to investigate this failure. Expected behavior is [expected]; observed behavior is [observed]. Here is the trigger and permitted evidence.
Replace placeholders with material you may share.
what it produces
5 sections- Reproducer or reproduction limit
- Tested hypotheses
- Causal evidence
- Repair
- Regression result
what to check
Call a workaround a mitigation unless the evidence supports the underlying cause and repair.
Your agent also reports checks it could not run.
Want fde to coordinate the project?
This task works on its own. Install fde to select instructions across customer work. Installing fde alone does not add each task as a separate menu entry.
npx skills add suboss87/fdeops --skill fdeBring FDEOps into your next customer task.
Use one task skill or let fde help you work across the project. Start with the notes or code you already have.