mcpbeat

Vouch Resolve Issue

vouchdev/vouch-resolve-issue

Use vouch's KB to ground a fix for a GitHub issue

276 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
120
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/vouchdev/vouch --skill vouch-resolve-issue

The instruction itself

1 sections, as written by the author

/vouch-resolve-issue

Wire vouch's kb_context into an issue-resolution flow: the KB should

inform the fix, and the act of solving should propose new claims that

make the next contributor faster.

Steps:

  • Parse $ARGUMENTS as a GitHub issue URL or <owner>/<repo>#<num> shorthand.

If neither, ask for clarification.

  • kb_context with the issue title + body — what does the KB already know

about this area? Show the top 5 claims.

  • Read the relevant code paths.
  • Propose the smallest fix (run the project's tests first to confirm the

bug reproduces).

  • After the fix is committed, propose at most three new claims via

kb_propose_claim that capture:

  • the root cause in one sentence (cited by the offending file:line),
  • the chosen fix pattern (cited by the patch commit), and
  • any policy/precedent established (only if novel).

Do not auto-approve. Leave the proposals in .vouch/proposed/ for the

maintainer to review with vouch approve after the PR merges.

How to use it

Copy the folder

Take vouchdev/vouch-resolve-issue from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.