$npx -y skills add vouchdev/vouch --skill vouch-resolve-issueUse vouch's KB to ground a fix for a GitHub issue
| 1 | # /vouch-resolve-issue |
| 2 | |
| 3 | Wire vouch's `kb_context` into an issue-resolution flow: the KB should |
| 4 | inform the fix, and the act of solving should propose new claims that |
| 5 | make the next contributor faster. |
| 6 | |
| 7 | Steps: |
| 8 | |
| 9 | 1. Parse `$ARGUMENTS` as a GitHub issue URL or `<owner>/<repo>#<num>` shorthand. |
| 10 | If neither, ask for clarification. |
| 11 | 2. `kb_context` with the issue title + body — what does the KB already know |
| 12 | about this area? Show the top 5 claims. |
| 13 | 3. Read the relevant code paths. |
| 14 | 4. Propose the smallest fix (run the project's tests first to confirm the |
| 15 | bug reproduces). |
| 16 | 5. After the fix is committed, propose **at most three** new claims via |
| 17 | `kb_propose_claim` that capture: |
| 18 | * the root cause in one sentence (cited by the offending file:line), |
| 19 | * the chosen fix pattern (cited by the patch commit), and |
| 20 | * any policy/precedent established (only if novel). |
| 21 | |
| 22 | Do not auto-approve. Leave the proposals in `.vouch/proposed/` for the |
| 23 | maintainer to review with `vouch approve` after the PR merges. |