hotfixlisted

# /bs:hotfix - Production Emergency Fast Path **Usage**: `/bs:hotfix <description> [--skip-verify] [--notify]` Fast-track for production emergencies: production down, critical bug, security vulnerability, revenue-impacting issue, data loss risk. For anything else, use `/bs:dev`. **Time:** 5-10 minutes ## What It Does 1. Create `hotfix/<description>` branch from main 2. Skip planning — implement fix directly 3. Minimal quality: tests (affected areas), lint, TypeScript, build 4. Create PR → auto-merge immediately 5. Deploy to production 6. Verify deployment (unless `--skip-verify`) 7. Alert team (if `--notify`) ## Implementation ### Step 0: Ensure Git Root ```bash GIT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null) || { echo "Not in a git repository"; exit 1; } cd "$GIT_ROOT" ``` ### Step 1: Create Hotfix Branch ```bash DESCRIPTION="$1" CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD) if [[ "$CURRENT_BRANCH" != "main" && "$CURRENT_BRANCH" != "master" ]]; then git checkout main && git pull fi [[ -n $(git status --porcelain) ]] && echo "❌ Uncommitted changes detected. Stash or commit first." && exit 1 BRANCH_NAME="hotfix/${DESCRIPTION}" git checkout -b "$BRANCH_NAME" echo "🚨 HOTFIX MODE | Branch: $BRANCH_NAME" ``` ### Step 2: Gather Emergency Context Ask user (be brief): - What's failing? - Error messages (if any) - Which file(s) likely need fixing? ### Step 3: Implement Fix Use TodoWrite minimally (Fix bug → Verify → Deploy). Implement directly. ### Step