swe-agent

Reproduce repository failures and generate minimal verified git patches.

43|2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/curated-skills/LinguaClaw --skill swe-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swe-agent
Source: https://github.com/curated-skills/LinguaClaw/tree/main/harnesses/artifacts/swe-agent
Command: npx skills add https://github.com/curated-skills/LinguaClaw --skill swe-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Resolving repository issues reliably by reproducing the failure, applying the smallest credible fix, and proving the fix with targeted verification.

Core Features & Use Cases

  • Reproduction-first workflow: turns an issue description into a concrete failing hypothesis and a rerunnable reproduction script.
  • Minimal patch crafting: edits the smallest non-test change set that addresses the root cause while preserving test integrity.
  • Verification with traceability: runs the relevant reproduction and test/verification commands and records what succeeded or failed, including reflection and retry guidance.

Quick Start

Ask the AI to run the swe-agent workflow: reproduce the issue with a file-backed script, implement the minimal fix using the provided editor workflow, then verify using the reproduction path and the relevant tests before handing off the final git patch.

Frequently Asked Questions about swe-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reproduce a bug and generate a minimal git patch for code editing?

A reproduction-first workflow creates a concrete failing hypothesis and a rerunnable script from your issue description. It then applies the smallest non-test code change set that addresses the root cause while preserving test integrity.

What is the best way to verify a bug fixing workflow after applying targeted edits?

Verification with traceability runs the relevant reproduction and test commands, recording what succeeded or failed. It includes final reflection that highlights risks and remaining uncertainty to guide any necessary retries.

Can I use a reproduction script to fix failing tests across different codebases?

Yes, this workflow applies to bug-fix scenarios where targeted edits, rerunnable reproduction scripts, and command-based verification are required across codebases. It uses a structured editor surface for focused iteration with recorded commands and output.

Why does my reproduction script fail to generate a minimal git patch for debugging?

Your reproduction script might fail to generate a minimal git patch if the reproduction-to-patch loop lacks a structured editor surface or command recording. Successful debugging requires creating a concrete failing hypothesis and applying the smallest non-test change set to address the root cause.

Do I need a reproduction-to-patch loop to ship minimal verified patches for repository issues?

Yes, you need a reproduction-to-patch loop to ship minimal verified patches for repository issues. This loop uses a structured editor surface for focused iteration, rerunnable scripts, command-based verification, and final reflection on risks and remaining uncertainty.