Menu
Evidence-driven debugging/incident workflow: reproduce, isolate, minimize, fix, verify, and prevent regressions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Short-lived feature branches; TDD + lint + merge-ready command as exit criteria before commit; push and merge to main (or user-directed flow). Do not default to asking the user to open a PR. Use when implementing a feature or non-trivial fix, when the user asks for branch/git workflow, or after substantial edits that should not stay uncommitted.
Change-aware quality pass: diff scope, readability, function size and control flow, comments where non-obvious, and alignment with project linting. Use before merge or with handoff when the user wants industry-style maintainability beyond what tests assert.
Define and maintain lightweight evaluations (acceptance criteria, regression checks, golden tests) so “green” is objective and repeatable.
Establish lightweight release discipline: definition of merge-ready, versioning/changelog habits, and safe rollout/rollback practices.
Maintain a lightweight risk register (top risks, triggers, mitigations, rollback) to prevent scope drift and improve decision quality.
Lightweight security review for agent work: secrets hygiene, safe logging, least privilege, and threat-model-lite checks.
| name | incident-triager |
| description | Evidence-driven debugging/incident workflow: reproduce, isolate, minimize, fix, verify, and prevent regressions. |
Use this skill when:
Goal: get to a minimal reproducible case, a minimal fix, and a verifiable outcome.
Define the incident
Reproduce
Isolate
Hypothesize (bounded)
Fix (minimal)
Verify
Document
