From blueprint
Emergency hotfix deployment: commit, push to staging branch, create PR to main, and merge. Use this skill when the user says "/hotfix", "emergency push", "hotfix to production", "push to staging and merge to main", "urgent deploy", "fast push to main", "deploy hotfix", or any request for an emergency/urgent deployment bypassing the normal /plan → /pr → /finish workflow. This is the fast lane: commit → push → PR → merge.
How this skill is triggered — by the user, by Claude, or both
Slash command
/blueprint:hotfixThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Fast-lane deployment for urgent fixes. Bypasses normal plan workflow.
Fast-lane deployment for urgent fixes. Bypasses normal plan workflow.
Read blueprint/.config.yml → language. If auto, detect from the user's messages. All generated content MUST be in the detected language. Skill instructions stay in English — only output changes.
Flow: commit → push to staging branch → PR staging→main → merge → GitHub Issue update
BRANCH=$(git branch --show-current)
STAGING_BRANCH=$(grep 'staging_branch:' blueprint/.config.yml | awk '{print $2}')
STAGING_BRANCH=${STAGING_BRANCH:-staging}
BASE=$(~/.blueprint/bin/blueprint meta 2>/dev/null | python3 -c "import sys,json; print(json.load(sys.stdin).get('base_branch','$STAGING_BRANCH'))")
Verify:
Stage and commit:
# Stage all changes (review what's being added)
git add -A
# Verify no unrelated files are staged — if unrelated files appear, unstage them
# Commit with hotfix emoji
git commit -m "🩹 hotfix: $DESCRIPTION"
# If on feature branch, push there first
git push origin "$BRANCH"
# If branch is not staging, merge into staging
if [ "$BRANCH" != "$STAGING_BRANCH" ]; then
git checkout "$STAGING_BRANCH"
git pull origin "$STAGING_BRANCH"
git merge "$BRANCH" -m "🔀 merge: $BRANCH into $STAGING_BRANCH (hotfix)"
git push origin "$STAGING_BRANCH"
git checkout "$BRANCH"
fi
GitHub Issue Detection: If $ARGUMENTS contains a GitHub issue reference (e.g., /hotfix #42 fix login timeout, /hotfix issue 42 fix crash), parse the issue number and include Closes #N in the PR body.
# Parse issue number from $ARGUMENTS if present
ISSUE_REF=""
# Check for patterns: #42, issue 42, or leading number
ISSUE_NUM=$(echo "$ARGUMENTS" | grep -oE '(#|issue ?)([0-9]+)' | grep -oE '[0-9]+' | head -1)
if [ -n "$ISSUE_NUM" ]; then
ISSUE_REF="Closes #$ISSUE_NUM"
fi
# Create PR
gh pr create \
--base main \
--head "$STAGING_BRANCH" \
--title "🩹 hotfix: $DESCRIPTION" \
--body "## Emergency Hotfix
**What:** $DESCRIPTION
**Why:** Urgent fix requiring immediate deployment
**Branch:** $BRANCH → $STAGING_BRANCH → main
### Changes
$(git log main..$STAGING_BRANCH --oneline)
### Verification
- [ ] Targeted tests pass
- [ ] Manual smoke test completed
### References
${ISSUE_REF}
"
PR_NUMBER=$(gh pr view "$STAGING_BRANCH" --json number -q .number)
gh pr merge "$PR_NUMBER" --merge --delete-branch=false
IMPORTANT: Do NOT delete the staging branch — it's permanent.
git add blueprint/ && git commit -m "🩹 hotfix: plan update for $DESCRIPTION" 2>/dev/null || true
AskUserQuestion — don't push broken code🩹 hotfix: commit formatAskUserQuestion tool, never plain text questionsUse $ARGUMENTS as the hotfix description. If empty, ask the user what the hotfix is for.
npx claudepluginhub skaisser/blueprint-pluginProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.