Guide structured diagnosis and evidence-based verification for code issue resolution.
npx skills add https://github.com/haposoft/cafekit --skill hapo-hotfix
Please help me install this Agent Skill. Skill: hapo:hotfix Source: https://github.com/haposoft/cafekit/tree/main/packages/spec/src/claude/skills/hotfix Command: npx skills add https://github.com/haposoft/cafekit --skill hapo-hotfix
This Skill enables efficient bug fixing by guiding the user through a structured process of diagnosis and verification, ensuring the root cause is identified and fixed properly before any code changes.
/hapo:hotfix "Identify and fix the authentication error in the API endpoint '/login'."
High-intent search queries and answers about installing and using this skill.
A systematic approach to bug fixing uses structured diagnosis to identify the root cause of code issues before applying changes. It ensures thorough bug elimination by following a six-step process that prioritizes evidence-first verification to prevent side effects.
To fix a critical production bug safely, follow a structured diagnosis process to isolate the root cause. Apply an evidence-first verification step to validate the fix, ensuring the original error is resolved without introducing new code issues.
The best way to conduct root cause analysis for code issues is using a customizable, structured workflow. This method guides you through thorough diagnosis and evidence-based verification before any code changes are made, ensuring proper bug elimination.
Yes, a code review is required after applying a hotfix to ensure quality assurance. The hotfix process depends on code review components to validate that the systematic bug fixing steps have successfully eliminated the issue without side effects.
Yes, the bug diagnosis workflow offers customizable processes based on the complexity and type of bug. This allows you to adapt the structured diagnosis and evidence-first verification steps to fit both simple code issues and critical production errors.
Your hotfix requires initial diagnosis to ensure the actual root cause is identified first. This structured approach prevents patching symptoms over root causes, using evidence-based verification to validate that the code changes resolve the issue properly.
tcfialhoAnalyze incident files to construct causal chains and identify root causes.
Jia-Hong-PengAutomate web application QA testing and generate structured bug reports.
bigeasyfreemanDebug code errors through evidence collection, hypothesis testing, and verification.
yocxy2Trace software symptoms to architectural root causes via a five-phase diagnostic workflow.
