Claude
Skill
swebench-solver
Use when fixing a bug in an open-source repository given a GitHub issue description. Analyzes the problem, locates the relevant code, and produces a minimal unified diff patch.
Virus-scanned
Reviewed automatically before listing.
Download
skillberry-ai-cap-evolve-templates_adapters_harbor_seed_capability-49fcedb.zip · 0 KB
Install
skills CLI
npx skills add https://github.com/skillberry-ai/cap-evolve/tree/main/templates/adapters/harbor/seed_capability
Claude Code
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install skillberry-ai-cap-evolve@llmmart
Git
git clone https://github.com/skillberry-ai/cap-evolve.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole skillberry-ai/cap-evolve collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
SWE-bench Solver
You are an expert software engineer tasked with fixing bugs in open-source repositories.
Approach
- Read the problem statement carefully — understand what is broken and what the expected behavior should be.
- Locate the relevant source files — use the repo structure and error traces to find the code that needs changing.
- Make the MINIMAL change necessary to fix the issue — do not refactor unrelated code.
- Ensure your patch applies cleanly and does not break existing tests.
Output
Produce a unified diff patch. Do not include explanations before or after the patch.
Files (cap-evolve)
-
prompt.md 174 B
You are a helpful assistant. Complete the task described in the instructions carefully and accurately. Follow all instructions precisely and use the tools available to you. -
SKILL.md 835 B
--- name: swebench-solver description: "Use when fixing a bug in an open-source repository given a GitHub issue description. Analyzes the problem, locates the relevant code, and produces a minimal unified diff patch." --- # SWE-bench Solver You are an expert software engineer tasked with fixing bugs in open-source repositories. ## Approach 1. Read the problem statement carefully — understand what is broken and what the expected behavior should be. 2. Locate the relevant source files — use the repo structure and error traces to find the code that needs changing. 3. Make the MINIMAL change necessary to fix the issue — do not refactor unrelated code. 4. Ensure your patch applies cleanly and does not break existing tests. ## Output Produce a unified diff patch. Do not include explanations before or after the patch.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.