skills.rest
HuynhHoangPhuc
HuynhHoangPhucCOMMUNITY
Explore all skills by this author →
GitHub

sl:fix

Diagnose bugs and implement minimal-change fixes with verification gates.

Updated Mar 12, 2026
Search Tags:#automation#workflow#debugging#diagnose#code-review#bug-fix
One-click install
npx skills add https://github.com/HuynhHoangPhuc/solon --skill sl-fix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sl:fix
Source: https://github.com/HuynhHoangPhuc/solon/tree/main/plugins/solon-core/skills/fix
Command: npx skills add https://github.com/HuynhHoangPhuc/solon --skill sl-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses before fixing. Never jump to code changes without understanding root cause.

Core Features & Use Cases

  • Structured diagnostic workflow to prevent premature fixes.
  • Gatekeeping steps and minimal-change implementation to reduce regression risk.
  • Use case: when a bug is reported, diagnose first, then implement a minimal fix with verification.

Quick Start

Diagnose issues first and apply a structured fix workflow.

Frequently Asked Questions about sl:fix

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

FAQPage Schema
How do I diagnose a code bug before jumping to a fix?▼

To diagnose a code bug before fixing, you need a structured workflow that identifies the root cause first. This approach prevents premature fixes by implementing gatekeeping steps and assessing risks before applying any minimal-change patch.

What is the best way to fix bugs in a CI workflow without causing regressions?▼

The best way to fix bugs in a CI workflow without regressions is to use a minimal-change implementation strategy. This method applies gatekeeping steps during the code review process to reduce regression risk and ensure the fix is verified.

Can I use a structured diagnosis workflow for software maintenance across different programming languages?▼

Yes, you can use a structured diagnosis workflow for software maintenance across different programming languages. It applies a universal diagnostic process to identify issues, assess risks, and implement minimal-change fixes regardless of the specific tech stack.

Why should I assess risk before implementing a bug fix in my codebase?▼

You should assess risk before implementing a bug fix to reduce regression chances. A structured workflow uses gatekeeping steps to evaluate the impact of minimal changes, ensuring that the patch resolves the diagnosed issue without destabilizing the existing codebase.

Does a minimal-change fix workflow work for code review automation?▼

Yes, a minimal-change fix workflow works for code review automation by integrating structured diagnosis and verification gates. It ensures that automated reviews focus on root cause resolution and risk assessment, preventing large, disruptive code modifications.

Related Skills

Explore More Software Engineering Skills→
RomualdPRomualdP

Bug Finding Methodology

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

Community
Basic
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
nicolanoviellnicolanoviell
2

code-review

Review code changes for bugs, style issues, and best practices.

Community
Intermediate
latestaiagentslatestaiagents
5

bug-reporting

Generates structured bug reports with reproduction steps and evidence templates for developers.

Official
Basic