skills.rest
kapilvirenahuja
kapilvirenahujaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

fix-it

Resolve software defects from root-cause analysis through verified merge.

3|Updated Jan 25, 2026
Search Tags:#bug fix#root cause analysis#regression testing#quality audit#autonomous shipping#checkpoint approval
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill fix-it
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-it
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/plays/fix-it
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill fix-it

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Fix-it eliminates the slow, error-prone process of manually debugging, designing, verifying, and shipping fixes by running a structured RCA-to-shipping workflow that ends with a merged patch and traceable evidence.

Core Features & Use Cases

  • RCA-driven defect resolution: Traces symptoms to the specific file and logic that is wrong, producing an auditable root cause artifact.
  • Fix design with alternatives: Produces a fix plan that explicitly considers alternatives and records rejection reasons.
  • Single checkpoint approval: Presents the RCA and fix design at exactly one human approval gate before implementation.
  • Independent verification before shipping: Ensures a failing regression test is authored and that an independent auditor verifies outcomes before merge.
  • Autonomous shipping end state: Commits, opens a PR, merges to main, and deletes the feature branch, linking back to the originating issue.

Quick Start

Use the fix-it skill to resolve an open bug issue by providing the issue number or running from a fix/ branch that contains that issue number.

Frequently Asked Questions about fix-it

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

FAQPage Schema
How do I automate bug fix shipping from root cause analysis to merge?▼

Autonomous bug fix shipping runs a structured root cause analysis to verified implementation workflow on a non-default branch, ending with a merged patch and traceable delivery evidence.

What is the best way to ensure a regression test is generated before merging a bug fix?▼

Generating a regression test before merging requires an independent quality auditor to verify outcomes and ensure a failing regression test is authored before autonomous shipping occurs.

Does autonomous bug fixing require human approval before implementation?▼

Autonomous bug fixing requires a single checkpoint approval where the root cause analysis and fix design are presented at exactly one human approval gate before implementation begins.

How do I trace a software defect to its specific root cause for an auditable fix?▼

Tracing a software defect to its root cause produces an auditable artifact by tracing symptoms to the specific file and logic that is wrong, alongside a fix plan considering alternatives.

Can I use root cause analysis to fix an issue directly on the main branch?▼

Root cause analysis defect resolution must be fixed on a non-default branch using a deterministic workflow, ensuring the feature branch is merged and deleted only after independent verification.

Related Skills

Explore More Software Engineering Skills→
jammindevjammindev

bug

Reproduce software bugs, add failing regression tests, and verify fixes.

Official
Advanced
alistairhendersoninfoalistairhendersoninfo

ship-it

Automate Git workflows from branch creation to pull request merge.

Community
Advanced
RomualdPRomualdP

Bug Finding Methodology

Identify bug root causes through a six-step diagnostic workflow.

Community
Basic
Eigo-Mt-FujiEigo-Mt-Fuji

bug-hunter

Guide structured bug investigation and root cause analysis with verification steps.

Community
Advanced