pilastdigit/trip-workflow/trip-hotfix

Hotfix Mode

You are now in hotfix mode - a streamlined workflow for urgent production fixes.

Warning: Only use this for genuine emergencies. For regular bugs, use the full TRIP workflow (TRIP-1-plan → TRIP-2-implement).

Your Task

Hotfix: $ARGUMENTS

Step 1: Assess Urgency

Before proceeding, confirm this is a genuine hotfix:

Use the `AskUserQuestion` tool to confirm urgency:

• Question: "Is this a production-critical issue that cannot wait for the normal TRIP workflow?"
• Options: "Yes — critical issue" (security vulnerability, data corruption, service outage, or critical user-facing bug), "No — regular bug" (redirect to TRIP-1-plan for proper workflow)

If "No": Redirect to TRIP-1-plan for proper workflow.

If "Yes": Proceed with hotfix.

Step 2: Create Hotfix Branch

git checkout main && git pull
git checkout -b hotfix/[short-description]

Step 3: Minimal Investigation

First, you MUST read ALL THE LINES of @docs/ARCHI.md then explore the codebase and read the files relevant to the issue.

Quickly identify:

1. Root cause (1-2 sentences)
2. Affected files (list)
3. Fix approach (brief)

No formal plan document needed.

Step 4: Implement Fix

• Focus only on the fix - no refactoring, no "while I'm here" improvements
• Minimal changes to resolve the issue
• Follow existing patterns from the codebase

Step 5: Quick Verification

• Manually test the fix
• Run relevant tests only: [test command] [affected files]
• Confirm the issue is resolved

Step 6: Version & Changelog

Version Bump

Increment patch version only (x.y.Z+1) in version file.

Minimal Changelog Entry

Add a row at the top of the table in docs/2-changelog/changelog_table.md:

| `x.y.z` | hotfix: [brief description] |

Create docs/2-changelog/vx.y.z.md:

# Changelog vx.y.z (DD-MM-YYYY) — Hotfix
 
-**Issue**: [What was broken]
-**Fix**: [What was done]
-**Root Cause**: [Brief explanation]

Step 7: Commit

git add -A && git commit -m "hotfix: [brief description]"

Step 8: Merge & Tag

git checkout main
git merge hotfix/[short-description]
git tag vx.y.z
git push && git push --tags
git branch -d hotfix/[short-description]

Step 9: Post-Hotfix

After the immediate crisis is resolved:

1. Document: Create a brief incident report in docs/6-memo/ if significant
2. Follow-up: If deeper fixes are needed, create a proper TRIP plan
3. Retrospective: Consider what could prevent similar issues

What This Workflow Skips

Compared to full TRIP:

• No interactive discovery questions
• No formal plan document
• No full code review checklist
• No ARCHI.md update (unless architecture changed)
• No README update (unless relevant)

These are acceptable trade-offs for genuine emergencies only.