skills.rest
swingerman
swingermanCOMMUNITY
Explore all skills by this author →
Website𝕏@miklosszanyiGitHub

fix

Drive bug fix workflows from report to closure with RED regression specs and mutation gates.

134|9|Updated Feb 16, 2026
Search Tags:#bug fix#gap analysis#regression testing#mutation testing#ATDD#spec pinning#hardening gate
One-click install
npx skills add https://github.com/swingerman/disciplined-agentic-engineering --skill fix-swingerman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/swingerman/disciplined-agentic-engineering/tree/main/engineer/skills/fix
Command: npx skills add https://github.com/swingerman/disciplined-agentic-engineering --skill fix-swingerman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The fix Skill turns messy bug reports into disciplined, verification-first repairs by requiring a failing regression spec before any code changes and closing with methodology feedback.

Core Features & Use Cases

  • Bug workflow from report to closure: Capture severity, source, repro/expected/actual, then progress through investigation, pinning, fixing, refining, verifying, hardening, and gap analysis.
  • Confirms the broken behavior (RED before change): Enforces that each pinned regression Given/When/Then must be RED on current code to ensure the defect is truly pinned.
  • Hardens against regression via mutation gates: Requires mutation and a bug-line gate so the regression spec is coupled to the actual buggy behavior, not just the fix outcome.
  • Produces methodology feedback: Runs a structured “why didn’t we catch it?” gap analysis using the closed category vocabulary, writing approved findings to the fix artifact.

Quick Start

Use the engineer.fix workflow by sending a bug report like “We’re seeing this error after login; here’s the stack trace and expected vs actual,” and include the source (e.g., Sentry issue link).

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 regression testing and spec pinning?▼

Spec pinning requires a failing Given/When/Then regression test that must be RED on current code before any fix is applied. This ensures the defect is truly pinned and repeatable before you implement the change that turns the spec GREEN.

What is the best way to prevent regressions when resolving a defect?▼

The best way to prevent regressions is applying mutation testing gates during the fix workflow. This requires a bug-line mutation confirmation to ensure your regression spec detects the actual broken behavior, not just the fix outcome.

How do I run a bug fix workflow from initial report to closure?▼

A bug fix workflow progresses from initial report through investigation, pinning, fixing, refining, verifying, hardening, and gap analysis. You capture severity, source, repro, and expected vs actual behavior to drive the defect to a closed state.

Why should I use a failing test before changing code to fix a bug?▼

You should use a failing test before changing code to confirm the broken behavior is truly pinned. Enforcing a RED regression spec before any code changes guarantees the defect is repeatable and verifiable across the pipeline.

What is a gap analysis for bug fixing and when do I need it?▼

A gap analysis for bug fixing is a structured methodology feedback loop asking why a defect was not caught earlier. You need it when closing a bug fix to write approved findings into the fix artifact and improve testing strategies.

Related Skills

Explore More Software Engineering Skills→
haidonglethqbhaidonglethqb

bug-report-qa

Generate structured bug reports with reproduction steps and Jira links.

Community
Intermediate
OKHP3OKHP3
2

okhp3-future-state-and-change-strategy

Design future-state processes and ADKAR-aligned change strategies from gap analysis.

Community
Intermediate
paulinghampaulingham
1

build-implementation

Convert architect-provided failing-test stubs into implemented code using the ATDD protocol.

Community
Advanced
valtterimelkkovaltterimelkko
1

test-driven-development

Enforces Red-Green-Refactor cycles for features and bug fixes using Jest or Vitest harnesses.

Community
Advanced