mcpbeat Sign in

Vouch Resolve Issue Agent Skill

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.

Other skills for the same job

different authors, same section of the catalogue
MCP Builder
by anthropics
vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

30k tokens scripts
Changelog Generator
by frostant
×9

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens
Finishing A Development Branch
by ZhanlinCui
×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1k tokens
MCP Builder
by JayZeeDesign
×7

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

37k tokens scripts
Vercel React Native Skills
by vercel-labs
vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens
Vercel React Best Practices
by ratacat
×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

34k tokens
Next Best Practices
by vercel-labs
vendor ×4

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

20k tokens
Using Git Worktrees
by ZhanlinCui
×4

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

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.