aboutsummaryrefslogtreecommitdiff
path: root/fix-issue
diff options
context:
space:
mode:
Diffstat (limited to 'fix-issue')
-rw-r--r--fix-issue/SKILL.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/fix-issue/SKILL.md b/fix-issue/SKILL.md
index adfed14..0b6e208 100644
--- a/fix-issue/SKILL.md
+++ b/fix-issue/SKILL.md
@@ -1,3 +1,8 @@
+---
+name: fix-issue
+description: Ticket-driven implementation workflow — fetch issue details from the tracker (Linear / GitHub Issues / Jira), create a branch, implement against acceptance criteria with tests, and commit/push. Reads the issue, verifies the delivery matches intent, handles the full branch lifecycle. Use when you have an issue ID or a well-scoped task ready to implement. Do NOT use for open-ended bug investigation without a clear fix path (use debug first), for tracing an error through a long call stack to its origin (use root-cause-trace), for small unticketed edits (just do them), or when requirements aren't yet clear (use brainstorm or arch-design). Companion to debug — fix-issue is the workflow scaffold around implementing a known fix; debug is the upstream investigative phase.
+---
+
# /fix-issue — Pick Up and Implement an Issue
Create a branch, implement the fix, test, and commit.