quick-fix

Apply minimal code changes to resolve specific bugs and verify with tests.

15|3|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/richardcb/oh-my-gemini --skill quick-fix-richardcb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quick-fix
Source: https://github.com/richardcb/oh-my-gemini/tree/main/skills/quick-fix
Command: npx skills add https://github.com/richardcb/oh-my-gemini --skill quick-fix-richardcb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the need for quick, precise fixes to specific bugs or issues without introducing unnecessary complexity or scope creep.

Core Features & Use Cases

  • Targeted Bug Fixing: Identifies and resolves isolated software defects.
  • Minimal Change Principle: Ensures only the necessary code is altered for the fix.
  • Verification: Includes steps to verify the fix through testing and type-checking.
  • Use Case: A user reports a critical but simple bug in production. This skill is used to apply a hotfix, verify its correctness, and prepare it for deployment.

Quick Start

Use the quick-fix skill to resolve the 'user login error' reported in the latest build.

Frequently Asked Questions about quick-fix

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

FAQPage Schema
How do I apply a minimal code change to fix a specific bug?

The smallest correct change for a bug fix involves locating the isolated defect and altering only the necessary code. This targeted patching approach prevents scope creep and avoids introducing unnecessary complexity into the software project.

When should I use a hotfix instead of refactoring my code?

Use a hotfix when resolving a critical, isolated bug in production rather than refactoring. Apply targeted patches to fix the specific defect immediately without altering broader system architecture or introducing unrelated structural changes.

How do I verify a software patch after applying a targeted fix?

Verify a software patch by running automated checks like tests and type checking. These verification steps ensure the targeted code change correctly resolves the specific bug without introducing new issues.

Can I use a minimal change approach for planning new software features?

No, a minimal change approach is not suitable for planning new features. This technique focuses exclusively on targeted bug fixing, patches, and hotfixes, deliberately avoiding broader planning, large-scale refactoring, or feature development.