litestar-fullstack-inertia: Command for Claude Code

GitHub Issue Fix Workflow

You are fixing issue: $ARGUMENTS

Workflow Overview

1. Load issue context
2. Investigate root cause
3. Implement fix with pattern compliance
4. Test thoroughly
5. Verify quality gates

---

Checkpoint 0: Load Issue Context

Fetch issue details:

gh issue view {issue_number}

Or if URL provided:

Use WebFetch to read issue content.

Extract key information:

• Issue description
• Expected behavior
• Actual behavior
• Steps to reproduce
• Related files mentioned

Output: "✓ Checkpoint 0 complete - Issue loaded: {title}"

---

Checkpoint 1: Root Cause Investigation

Use debug tool for complex issues:

mcp__pal__debug(
    step="Investigating issue #{issue_number}...",
    step_number=1,
    total_steps=3,
    next_step_required=true,
    findings="Issue description: ...",
    hypothesis="The root cause might be..."
)

Search for related code:

# Find related files
grep -r "{keyword}" app/ --include="*.py"
grep -r "{keyword}" resources/ --include="*.tsx"

# Find error sources
grep -r "{error_message}" app/

Read related files:

cat {related_file}

Document findings:

## Investigation Findings

### Root Cause
[Description of the root cause]

### Affected Files
- `path/to/file.py:line` - Description
- `path/to/file.tsx:line` - Description

### Proposed Fix
[Description of the fix approach]

Output: "✓ Checkpoint 1 complete - Root cause identified"

---

Checkpoint 2: Pattern Check

Before implementing fix, verify patterns:

Read similar implementations to understand existing patterns:

# Find similar code
grep -r "similar_pattern" app/

Ensure fix follows:

• Existing code style
• Type hint conventions (T | None)
• Error handling patterns
• Test patterns

Output: "✓ Checkpoint 2 complete - Patterns verified"

---

Checkpoint 3: Implement Fix

Make minimal, focused changes:

• Only fix what's broken
• Don't refactor surrounding code
• Don't add unrelated improvements