skills.rest
bjornjee
bjornjeeCOMMUNITY
Explore all skills by this author →
GitHub

fix

Reproduce a software defect in an isolated git worktree, then validate a minimal fix with tests.

19|2|Updated Mar 30, 2026
Search Tags:#workflow automation#root cause analysis#bug fixing#git worktree#test-first#CI verification#repro steps
One-click install
npx skills add https://github.com/bjornjee/agent-dashboard --skill fix-bjornjee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/bjornjee/agent-dashboard/tree/main/adapters/claude-code/skills/fix
Command: npx skills add https://github.com/bjornjee/agent-dashboard --skill fix-bjornjee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you diagnose and correct a software bug with a disciplined, evidence-first workflow that reproduces the issue in an isolated git worktree before changing code.

Core Features & Use Cases

  • Reproduce-first, test-first debugging: Collects grounded evidence, writes a minimal failing test, and verifies the failure before diagnosing.
  • Isolated worktree safety: Creates a dedicated fix/<name> branch and separate worktree from the latest main, with environment files copied to preserve exact relative paths.
  • End-to-end fix with verification: Implements the minimal code change, then runs the failing test and the full test suite to confirm the fix.

Quick Start

Use the fix skill to diagnose and resolve a bug described by your error message, stack trace, or reproduction steps in an isolated worktree.

Frequently Asked Questions about fix

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

FAQPage Schema
How do I fix a bug using a git worktree and test-first workflow?▼

To fix a bug using a git worktree, you create an isolated fix branch, write a failing test to reproduce the issue, implement a minimal code change, and validate the fix with the full test suite.

What is evidence-driven root cause analysis for software defects?▼

Evidence-driven root cause analysis grounds bug diagnosis in logs, traces, or reproducible metrics, verifying the defect with a failing test before applying any code corrections to ensure accurate repair.

How do I isolate bug reproduction steps in a fresh git worktree?▼

You isolate bug reproduction by creating a dedicated fix branch in a separate worktree from main, copying environment files to preserve exact relative paths, and running a failing test to confirm the defect.

Can I use this test-first debugging approach for projects requiring CI verification?▼

Yes, test-first debugging applies to projects that can be set up in a fresh worktree and verified via CI, requiring both targeted failing-test reproduction and full test suite validation to confirm the minimal fix.

Why should I reproduce a bug with a failing test before diagnosing the root cause?▼

Reproducing a bug with a failing test before diagnosing the root cause ensures the issue is grounded in actual evidence, preventing speculative fixes and confirming the defect exists before applying minimal code changes.

What are the limitations of worktree isolation for bug fixing?▼

Worktree isolation for bug fixing requires the issue to be reproducible in a fresh environment setup and verifiable via automated tests, limiting its use for non-deterministic defects or issues lacking clear repro steps.

Related Skills

Explore More Software Engineering Skills→
www-zaq-aiwww-zaq-ai
66

worktree-setup

Create an isolated git worktree for a specified branch with configuration files.

Official
Intermediate
mr-daedaliummr-daedalium
107

land-and-deploy

Merge PRs, trigger deployment, and verify canary health in CI/CD pipelines.

Community
Advanced
heyallencaoheyallencao
118

ks-verify

Run automated test suites and coverage checks to validate code claims.

Community
Intermediate
donygeorgedonygeorge
2

fix

Diagnose software defects and implement validated incremental fixes.

Community
Advanced