fix

Implements small scoped bug fixes with reproduction, root cause analysis, and full Definition of Done checks.

3|Updated May 2, 2026
One-click install
npx skills add https://github.com/JuanTrujilloDev/agent-config-template --skill fix-juantrujillodev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/JuanTrujilloDev/agent-config-template/tree/main/cursor/.claude/skills/fix
Command: npx skills add https://github.com/JuanTrujilloDev/agent-config-template --skill fix-juantrujillodev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Small bugs with obvious causes do not need a full spec, brief, and design phase, but skipping review and testing entirely leads to sloppy patches. This Skill provides a fast path for tiny, well-understood fixes while still enforcing reproduction, root cause analysis, formatting, linting, testing, and review. ## Core Features & Use Cases - Reproduce Red First: Requires a failing test or failing command that only goes green when the bug is fixed before naming the cause. - Root Cause Statement: Captures the cause in one or two sentences plus 2-4 verifiable success criteria, with no separate brief or plan documents. - Typed Branch Workflow: Checks out a fix/ or hotfix/ branch, implements a surgical change, and runs the full Definition of Done including judge and security-reviewer subagents. - Use Case: A button on your web app submits a form twice because of a missing disabled state. Run /fix prevent double form submission on save button to reproduce the failure, patch the handler, run tests and review, and commit on a typed branch. ## Quick Start Ask the agent to run /fix followed by a one-sentence description of the small bug you want repaired.

Frequently Asked Questions about fix

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

FAQPage Schema
How do I quickly fix a small bug without writing a full spec?▼

Use the /fix command with a one-sentence description of the bug. It skips the brief and design phases but still requires a failing reproduction, a stated root cause, and the full Definition of Done before committing.

When should I use /fix instead of /feature?▼

Use /fix only when the change is small, scoped, and has an obvious cause. If the work adds a model, migration, or endpoint, or you cannot scope it in one sentence, switch to /feature which includes the brief and Design First steps.

Does /fix skip code review and testing?▼

No. /fix skips the spec and design artifacts but never the Definition of Done. It still runs format, lint, and test commands, spawns a judge reviewer, and adds a security-reviewer when the fix touches auth, permissions, or data.

What happens if I cannot reproduce the bug in one step?▼

If a red reproduction cannot be obtained in one step, the workflow stops and switches to /feature. When reproduction does not isolate the cause, it writes 2-4 ranked falsifiable hypotheses and tests them one variable at a time.

What branch naming does /fix use for bug fixes?▼

It checks out a typed branch named fix/<ticket>-<slug>, or hotfix/<slug> for urgent production issues. Work is never committed directly on the default branch.