skills.rest
swghosh
swghoshCOMMUNITY
Explore all skills by this author →
Website𝕏@SwG_GhoshGitHub

fix

Implement minimal code changes from root-cause analysis with quality checks.

Updated May 5, 2026
Search Tags:#documentation#error handling#root cause analysis#code implementation#bugfix#quality checks
One-click install
npx skills add https://github.com/swghosh/ambient-workflows --skill fix-swghosh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/swghosh/ambient-workflows/tree/main/workflows/bugfix/.claude/skills/fix
Command: npx skills add https://github.com/swghosh/ambient-workflows --skill fix-swghosh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn root-cause analysis into a minimal, maintainable code change that fixes a bug without introducing regressions.

Core Features & Use Cases

  • Fix implementation from diagnosis: Reviews the recommended remediation approach and plans the smallest safe change that addresses the underlying cause.
  • Change safety and quality gates: Creates a feature branch, implements targeted fixes, and runs formatting, linting, build/compile, and security checks.
  • Verification and documentation: Ensures error paths and state/condition enumeration are complete, then writes implementation notes with file/line references for traceability.

Quick Start

Implement the bug fix for the diagnosed issue by reviewing the root-cause artifacts (if present), creating the required feature branch, applying the minimal code changes, running quality checks, and writing implementation notes to artifacts/bugfix/fixes/implementation-notes.md.

Frequently Asked Questions about fix

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

FAQPage Schema
How do I implement a minimal bug fix from a root-cause analysis?▼

You can ensure bug fixes do not introduce regressions by applying minimal maintainable code modifications, validating state and condition enumerations, completing error paths, and running formatting, linting, build, and security checks.

What is the best way to document bug fix implementation notes for traceability?▼

The best way to document bug fix implementation notes is to produce artifact-based markdown files containing specific file and line references that trace the minimal code changes back to the original root-cause analysis.

Do I need prior diagnosis artifacts to use this bug fix implementation approach?▼

You need prior diagnosis artifacts if present, as this approach requires a produced fix strategy from a root-cause analysis phase to plan the smallest safe code change that removes faulty behavior.

What quality checks should I run after applying a bugfix to a code repository?▼

After applying a bugfix to a code repository, you should run project-appropriate quality checks including formatting, linting, build or compile, and security checks to validate the targeted fixes.

Related Skills

Explore More Software Engineering Skills→
rory-datarory-data

debugging-dags

Diagnose failed Airflow DAGs and provide root-cause remediation.

Community
Advanced
quaid-appquaid-app
3

git-workflow

Enforce a dev-first three-branch model with issue-based workflows and PR merges.

Official
Intermediate
KimjimanKimjiman

verification-loop

Run build, type, lint, test, security, and diff checks before pull requests.

Community
Advanced
YairamaYairama

coding-guidelines

Guide deliberate software changes with minimal scope and verification.

Community
Basic