| name | scip-triage-issue |
| description | Triage issues with scip-query evidence. Use for bug reports, GitHub issues, failing tests, support reports, TODOs, vague defects, root-cause packets, issue bodies, or test-first fix plans. |
| commands | [{"template":"scip-query files <issue-term>","when":"Map ownership: locate files for the reported term."},{"template":"scip-query trace <entry-or-error-symbol>","when":"Trace the failing path: definition plus every reference."},{"template":"scip-query code <entry-or-error-symbol>","when":"Trace the failing path: read the exact source."},{"template":"scip-query call-graph <entry-symbol>","when":"Trace the failing path: callers and callees."},{"template":"scip-query similar <suspect-symbol> --json --full","when":"Compare and bound: nearby implementations for missing handling."},{"template":"scip-query affected <symbol> --json","when":"Compare and bound: transitive impact bound for the fix plan."}] |
scip-triage-issue
Use this skill to turn a report into a grounded fix packet. Triage is the evidence pass that determines whether the issue is reproducible, where it enters the codebase, what root cause is likely, and what test should fail before the fix.
Load shared mechanics from ../_shared/SKILL.md.
Commands for this skill
| Command | Purpose | When |
|---|
scip-query files <issue-term> | Find files matching a pattern | Map ownership: locate files for the reported term. |
scip-query trace <entry-or-error-symbol> | Trace a symbol: definition + all references | Trace the failing path: definition plus every reference. |
scip-query code <entry-or-error-symbol> | Read the source code for a symbol (bounded to its definition range) | Trace the failing path: read the exact source. |
scip-query call-graph <entry-symbol> | Show incoming callers and outgoing callees for a symbol | Trace the failing path: callers and callees. |
scip-query similar <suspect-symbol> --json --full | Find heuristic function similarity candidates from callee fingerprints | Compare and bound: nearby implementations for missing handling. |
scip-query affected <symbol> --json | Transitive closure of symbols that could break if this symbol changes | Compare and bound: transitive impact bound for the fix plan. |
Use this shortlist first. Open ../_shared/SKILL.md only when it is insufficient.
Rules
- Do not file or implement from the title alone.
- Use scip-query for code evidence: entry points, references, call flow, data flow, blast radius, and similar implementations.
- Prefer a failing test plan before a code plan.
- If the user asks only for triage, stop at the packet. If they asked to fix it too, implement after the packet is clear.
Workflow
1. Normalize the report
Record summary, observed behavior, expected behavior, reproduction, affected surface, severity, user impact, and logs/screenshots/tests/links.
Ask the user only for product intent, credentials, private data, or external system state the repo cannot answer.
This step is complete only when missing facts are either recovered or named.
2. Map ownership
scip-query files <issue-term>
scip-query outline <candidate-file>
scip-query system <module-or-scope>
scip-query surface <module-or-scope>
Use kind-counts and by-kind for broad subsystems.
This step is complete only when likely owner files and surfaces are named.
3. Trace the failing path
scip-query trace <entry-or-error-symbol>
scip-query code <entry-or-error-symbol>
scip-query call-graph <entry-symbol>
scip-query dataflow <state-or-input-symbol>
scip-query slice <state-or-input-symbol>
For stack traces, read the exact range with scip-query code 'file:start-end'.
This step is complete only when a suspected root cause is tied to source evidence or labeled unproven.
4. Compare and bound
scip-query similar <suspect-symbol> --json --full
scip-query similar <suspect-symbol> <comparison-symbol> --plan
scip-query similar-files <suspect-file> --json --full
scip-query co-change <suspect-file> --json --full
scip-query change-surface <suspect-file> --json --full
scip-query affected <suspect-symbol> --json
This step is complete only when the packet has a narrow test shape and impact bound.
Packet
## Issue
<one-sentence mismatch>
## Reproduction
<steps, command, failing test, or missing data>
## Evidence
- <scip-query command>: <fact>
## Suspected Root Cause
<earliest code fact that explains the symptom>
## Impact
- users/surfaces affected
- blast radius
## Fix Plan
1. Add or update failing test/smoke check.
2. Make the smallest code change.
3. Run targeted test.
4. Invoke `scip-verify`.
## Open Questions
- <product intent or external state only>
If no root cause is proven, label the issue needs reproduction or needs product decision.
