LING71671 gstack-investigate
Use this skill to diagnose before fixing.
Workflow
- State the observed symptom and the expected behavior.
- Reproduce the issue with the smallest command, UI flow, fixture, or log slice available.
- Trace the relevant path through the code before proposing a fix.
- Form at least three plausible causes.
- Test the causes with targeted checks, logs, assertions, or isolated commands.
- Pick the cause with the strongest evidence.
- Apply the smallest fix that addresses that cause.
- Re-run the original reproduction and one nearby regression check.
Rules
- Do not fix before reproduction or strong evidence.
- If one attempted fix fails, record why and try a different strategy.
- Prefer direct runtime evidence: command output, logs, API responses, persisted state, or failing tests.
- Keep unrelated refactors out of the fix.
Output
Report:
- Symptom
- Root cause
- Fix
- Verification command or manual check
- Residual risk