skills.rest
avav25
avav25COMMUNITY
Explore all skills by this author →
GitHub

bugfix

Coordinate a traceable bugfix workflow with root-cause analysis and regression tests.

2|Updated Mar 19, 2026
Search Tags:#quality-assurance#software-engineering#bugfix#root-cause-analysis#regression-testing
One-click install
npx skills add https://github.com/avav25/ai-assets --skill bugfix-avav25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bugfix
Source: https://github.com/avav25/ai-assets/tree/main/.windsurf/skills/bugfix
Command: npx skills add https://github.com/avav25/ai-assets --skill bugfix-avav25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end bugfix workflows that gather evidence, identify the affected stack, implement root-cause fixes with minimal blast radius, add regression coverage, and verify results.

Core Features & Use Cases

  • Capture bug details: reproduction steps, environment, and impact.
  • Analyze the environment and affected stack to determine the correct root-cause area.
  • Plan and implement a minimal, verifiable fix with regression tests and documentation.
  • Verify fixes across environments and communicate results.

Quick Start

Describe the defect, reproduce it, and follow the Bugfix steps to implement a minimal, verifiable fix.

Frequently Asked Questions about bugfix

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

FAQPage Schema
How do I perform root-cause analysis for a software defect across different environments?▼

Root-cause analysis for a software defect involves gathering evidence, analyzing the affected environment and stack, and planning a minimal verifiable fix. This workflow ensures you identify the correct root-cause area before implementing code changes.

What is the best way to plan regression testing after implementing a bugfix?▼

The best way to plan regression testing is to define verification criteria and add regression coverage during the bugfix. This ensures the minimal verifiable fix is verified across environments and prevents future regressions.

How do I reproduce a bug and document reproduction steps for root-cause analysis?▼

To reproduce a bug for root-cause analysis, you must capture specific bug details including reproduction steps, environment details, and impact. Documenting these elements ensures a traceable bugfix workflow and accurate defect resolution.

Can I use a structured bugfix workflow for both frontend and DevOps issues?▼

Yes, a structured bugfix workflow applies across codebases and teams for frontend, backend, DevOps, and data issues. It coordinates root-cause analysis and code changes regardless of the affected technical stack.

Why should I implement minimal-change fixes when resolving software defects?▼

You should implement minimal-change fixes to ensure a safe blast radius and maintain software quality assurance. This approach limits unintended side effects while allowing verifiable fixes across different environments.

Related Skills

Explore More Software Engineering Skills→
simotasimota
68

Scout

Analyze error reports and trace execution flows to identify software bug root causes.

Community
Advanced
DatTran26DatTran26

ck:test

Execute unit, integration, e2e, and UI tests with coverage reports.

Community
Advanced
adiytharpansaadiytharpansa

Agentic Coding

Enforce contract-driven implementation and verification workflows for AI-assisted software development.

Community
Advanced
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced