Design minimal safe code fixes with before/after snippets and tests.
npx skills add https://github.com/pcortes/swarm-attack --skill fix-planner
Please help me install this Agent Skill. Skill: fix-planner Source: https://github.com/pcortes/swarm-attack/tree/main/default-skills/fix-planner Command: npx skills add https://github.com/pcortes/swarm-attack --skill fix-planner
Design fixes that precisely address root causes with minimal risk, avoiding large, disruptive changes.
Submit the root-cause analysis and the affected files; the skill outputs a patch plan including file changes, rationale, and tests.
High-intent search queries and answers about installing and using this skill.
A minimal code fix identifies the smallest change addressing the root cause. Start with root-cause analysis of the bug, then specify exact before/after code snippets for each file, create regression tests, assess risk, and document a rollback plan to ensure backward compatibility.
A patch design includes precise before/after code snippets for each affected file, test cases covering regressions and edge cases, risk assessment, clear justification for each change, and a rollback plan. This ensures minimal, safe fixes that avoid large disruptive changes.
Regression tests verify the fix resolves the bug without breaking existing functionality. Plan tests covering the specific bug scenario, edge cases, and related code paths. Document test cases alongside the patch design to ensure coverage constraints and backward compatibility.
Yes, this approach suits production hotfixes. The minimal design, exact code specification, risk assessment, and rollback plan reduce deployment risk. Requires a documented root-cause analysis before designing the patch to ensure the fix is targeted and safe.
Backward compatibility is a core constraint. The patch design rejects changes that break existing interfaces or behavior. If a breaking change is necessary, it must be explicitly documented, justified, and included in the risk assessment and rollback plan.
Yes, edge-case handling is required. The patch design identifies boundary conditions, unusual inputs, and related code paths that might be affected. Test cases must cover these scenarios to prevent regressions in unexpected contexts.
VoDaiLoczAnalyze systemic issues using 5 Whys and Fishbone diagrams.
oxieCategorize and patch CI and deployment check failures until all pass.
RheasilviaRun static security analysis, regression tests, and subagent review before code commits.
CaptainPhantasyApply a four-phase framework to identify root causes before implementing fixes.
