bugfix-implement

Implement constrained code fixes on a dedicated bugfix branch.

1|Updated Apr 9, 2026

Search Tags:#typescript #root cause #git workflow #implementation #bugfix #quality checks #strategy compliance

Ready to run

npx skills add https://github.com/noni2she/agent-fix --skill bugfix-implement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bugfix-implement
Source: https://github.com/noni2she/agent-fix/tree/main/skills/bugfix-implement
Command: npx skills add https://github.com/noni2she/agent-fix --skill bugfix-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

根據已完成的 bugfix-analyze 分析報告，將明確的 root cause 與 Fix Strategy 轉化為可提交的程式碼修復，同時確保工程驗證流程與風險控管不被跳過。

Core Features & Use Cases

Strategy-locked Implementation：強制遵守 analyze.md 的 Fix Strategy（DIRECT 或 TACTICAL），禁止自行變更。
Pre-implementation Validation：在修改前核對 root_cause_file、root_cause_line 與 impacted_files 的真實存在與一致性，避免錯修。
Git Workflow Guardrails：要求在 bugfix/<issue-id>-<description> 分支完成修復流程，並在提交前執行 quality_checks。
Tactical Fix Guarding：核心共用元件採 wrapper/guard clause 並加上 TODO 註解標記技術債，限制侵入式修改範圍。
Commit-ready Reporting：輸出修復報告並依任務指定路徑持久化，協助後續測試與追蹤。

Quick Start

Use bugfix-implement to implement a fix by providing the analyze report path produced by bugfix-analyze for the given issue.

Frequently Asked Questions about bugfix-implement

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

FAQPage Schema

How do I implement a code fix from a validated root cause analysis report?▼

To implement a code fix from a validated root cause analysis, provide the analyze report path to translate the locked Fix Strategy, root cause file, and impacted files into a constrained code modification on a dedicated bugfix branch.

Can I change the Fix Strategy during bugfix implementation if I find a better solution?▼

You cannot change the Fix Strategy during bugfix implementation because the process enforces strategy-locked implementation, strictly prohibiting deviations from the DIRECT or TACTICAL strategy defined in the prior analysis report.

What git workflow do I need to follow when applying a bugfix to a TypeScript project?▼

Applying a bugfix requires satisfying git workflow guardrails by completing the code modification on a dedicated bugfix branch and running project-defined lint, type, and test validations as commit-time quality checks before submission.

How does a TACTICAL bugfix strategy limit modifications to core shared components?▼

A TACTICAL bugfix strategy limits modifications to shared components by enforcing wrapper or guard clause implementations, adding TODO comments to mark technical debt, and restricting the scope of intrusive code changes.

What pre-implementation validations are required before modifying the root cause file?▼

Pre-implementation validation requires verifying the actual existence and consistency of the root cause file, root cause line, and impacted files specified in the analysis report to prevent incorrect code modifications.

Does bugfix implementation automatically handle TypeScript lint and type checks before committing?▼

Bugfix implementation handles TypeScript lint and type checks by running the project-defined lint, type, and test validations as required commit-time quality checks before finalizing the code fix on the bugfix branch.