name	fix-issue
description	Use when fixing a GitHub issue — reproduce, trace root cause, fix, add regression test
disable-model-invocation	true
arguments	[{"name":"issue","description":"GitHub issue number or URL","required":true}]

Fix Issue Workflow

When to use

Fixing a tracked GitHub issue: reproduce → trace root cause → fix → add regression test.
Any bug fix that needs a failing test written first (TDD approach).
Investigating an issue report where the reproduction steps or root cause are unclear.

Step 1: Load Issue Context

Fetch issue details: gh issue view $issue --json title,body,labels,comments
Read all comments for additional context
Identify: expected behavior, actual behavior, reproduction steps

Step 2: Reproduce

Set up reproduction environment based on issue description
Write a failing test that captures the bug (TDD approach)
If cannot reproduce — ask user for more context, do NOT guess

Step 3: Trace Root Cause

Use Grep/Glob to find relevant code paths
Trace execution flow from entry point to failure
Identify the ROOT CAUSE, not symptoms
Check DECISIONS.md for related past decisions

Step 4: Checkpoint

git commit current state: checkpoint: before fix-issue #$issue

Step 5: Fix

Fix at the root cause level, NOT overlay/patch
Follow Constructor Pattern: if fix grows file >200 lines, decompose
Ensure fix doesn't break other functionality

Step 6: Verify

Run the failing test — must pass now
Run full test suite — no regressions
If test suite doesn't exist, create at minimum:
- Test for the specific bug (regression test)
- Test for the happy path of affected function

Step 7: Commit

fix: <description of what was fixed> (closes #$issue)
Update TODO.md if issue was tracked there

Más de este repositorio

mismo repositorio

research

KeiSeiLab/KeiSeiKit

Deep research on any topic using parallel agents, web search, and cross-referencing. Use when user asks to research, investigate, or deeply analyze a topic, technology, library, or concept. Triggers on keywords like "research", "investigate", "deep dive", "find out everything about". Supports `--angle` presets for common specializations (competitors, design-refs).

2026-06-017

animate

KeiSeiLab/KeiSeiKit

Gateway router for web animation work. Picks between /scroll-animation, /motion-design, or /ai-animation via one AskUserQuestion call, then hands off. Does NOT implement animation — the downstream skills remain the source of truth for their respective domains.

2026-05-307

batch-workflow

KeiSeiLab/KeiSeiKit

Use when running multi-skill pipelines — new-feature, marketing-launch, design-to-code, web-creation, full-audit, rag-setup workflows

2026-05-307

compose-solution

KeiSeiLab/KeiSeiKit

Meta-orchestrator — converts a free-text task description into the right artefact(s) (agent, skill, hook, rule, or block) by composing existing KeiSeiKit primitives. Pure-click decision chain except the single intake field. Enriches `_blocks/` over time via Phase 6 block-augmentation — the kit gets smarter with every invocation.

2026-05-307

design-inspiration

KeiSeiLab/KeiSeiKit

Deprecated alias for /research with the design-refs angle preset. Routes to /research focused on design patterns, visual archetype references, and award-winning site teardowns.

2026-05-307

dev-guard

KeiSeiLab/KeiSeiKit

Continuous parallel quality gate during development — 3 backend agents (security/perf/structure) check every significant code change in real-time. Run after writing code, before committing.

2026-05-307

name	fix-issue
description	Use when fixing a GitHub issue — reproduce, trace root cause, fix, add regression test
disable-model-invocation	true
arguments	[{"name":"issue","description":"GitHub issue number or URL","required":true}]

Fix Issue Workflow

When to use

Fixing a tracked GitHub issue: reproduce → trace root cause → fix → add regression test.
Any bug fix that needs a failing test written first (TDD approach).
Investigating an issue report where the reproduction steps or root cause are unclear.

Step 1: Load Issue Context

Fetch issue details: gh issue view $issue --json title,body,labels,comments
Read all comments for additional context
Identify: expected behavior, actual behavior, reproduction steps

Step 2: Reproduce

Set up reproduction environment based on issue description
Write a failing test that captures the bug (TDD approach)
If cannot reproduce — ask user for more context, do NOT guess

Step 3: Trace Root Cause

Use Grep/Glob to find relevant code paths
Trace execution flow from entry point to failure
Identify the ROOT CAUSE, not symptoms
Check DECISIONS.md for related past decisions

Step 4: Checkpoint

git commit current state: checkpoint: before fix-issue #$issue

Step 5: Fix

Fix at the root cause level, NOT overlay/patch
Follow Constructor Pattern: if fix grows file >200 lines, decompose
Ensure fix doesn't break other functionality

Step 6: Verify

Run the failing test — must pass now
Run full test suite — no regressions
If test suite doesn't exist, create at minimum:
- Test for the specific bug (regression test)
- Test for the happy path of affected function

Step 7: Commit

fix: <description of what was fixed> (closes #$issue)
Update TODO.md if issue was tracked there