speckit-fixit-run

Map software bugs to spec-kit artifacts and apply minimal approved code changes.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-fixit-run
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-fixit-run
Source: https://github.com/B0yZ4kr14/OrthoPlus-Enterprise/tree/main/.specify-backups/20260518-141826/_agents/skills/speckit-fixit-run
Command: npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-fixit-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you resolve software bugs by grounding the fix in existing specification artifacts, ensuring the change matches intended behavior rather than guesswork.

Core Features & Use Cases

  • Spec-aware debugging: Loads the relevant spec context (spec/tasks/optional plan/constitution) to map the bug to the correct story, functional requirements, and acceptance scenarios.
  • Minimal-change patching: Proposes a targeted fix and, after approval, applies the smallest code change expected to resolve the issue.
  • Plan-then-act safety: Always produces a proposed fix plan first and waits for explicit user approval before modifying code.

Quick Start

Send an instruction like: "Fix the bug where appointment scheduling fails when the patient has no insurance plan selected."

Frequently Asked Questions about speckit-fixit-run

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

FAQPage Schema
How do I fix a software bug using spec-kit artifacts?▼

To fix a software bug using spec-kit artifacts, the Skill maps the user-described issue to existing acceptance criteria and spec headers, proposes a minimal code patch, and waits for your explicit approval before applying changes.

What is spec-aware bug fixing and how does it work?▼

Spec-aware bug fixing resolves issues by loading relevant spec.md and tasks.md context to map the defect to intended behavior and acceptance scenarios, ensuring the code patch matches specifications rather than guesswork.

Do I need a .specify directory to use spec-aware debugging?▼

Yes, spec-aware debugging requires a .specify directory containing feature folders with spec.md and tasks.md, and you must run the check-prerequisites script before mapping the bug to acceptance criteria.

Can I modify spec artifacts when applying a minimal code patch?▼

No, the approval workflow strictly prohibits modifying spec artifacts; it only proposes and applies the smallest targeted code change expected to resolve the bug after you review the fix plan.

What is the best way to ensure code patches match acceptance criteria?▼

The best way to ensure patches match acceptance criteria is using an approval workflow that progressively loads spec and task headers to ground the minimal change in the intended functional requirements before modifying code.