git-commit-hotfix

A guided Git process for committing urgent fixes, commonly called hotfixes, and managing their pull requests. A pull request is a proposed code change that teammates review before it is merged.

In plain words
What is it for?
Use it to validate a hotfix branch, update its pull request, prepare review information, check documentation, and assess whether the fix is ready to deploy.
Why use it?
It helps keep urgent changes limited, documented, reviewed, and checked for deployment readiness. It also verifies that the work is on the expected hotfix branch.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/oakensoul/nextjs-cursor-prompts/git-commit-hotfix
Clone the repo
git clone --depth 1 https://github.com/oakensoul/nextjs-cursor-prompts

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 4,650 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.04650
Opus 5 $0.00000 $0.02325
Sonnet 5 $0.00000 $0.00930
Haiku 4.5 $0.00000 $0.00465

Measured 2d ago against content hash 93014807b24b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-commit-hotfix scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/prompts/git/git-commit-hotfix.mdc · 617 lines

How it starts

The opening of the file, as written. The whole thing — 617 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Hotfix Commit and Pull Request Management

This prompt provides specialized commit process for hotfixes with automated documentation updates, code review integration, and pull request management.

🎯 HOTFIX COMMIT OBJECTIVES:

  1. COMMIT hotfix changes with comprehensive documentation and traceability
  2. UPDATE pull request automatically with implementation details
  3. GENERATE automated code review summary and recommendations
  4. VALIDATE final deployment readiness before pushing to remote
  5. COORDINATE team communication and next steps for deployment

📋 PRE-COMMIT VALIDATION:

STEP 1: Final Hotfix Validation

Branch and Environment Verification:
# Verify we're on the correct hotfix branch
CURRENT_BRANCH=$(git branch --show-current)
if [[ ! "$CURRENT_BRANCH" =~ ^hotfix/ ]]; then
    echo "❌ ERROR: Not on a hotfix branch. Current: $CURRENT_BRANCH"
    exit 1
fi

echo "✅ Validated hotfix branch: $CURRENT_BRANCH"

# Extract issue information
ISSUE_ID=$(echo $CURRENT_BRANCH | cut -d'-' -f2)
DESCRIPTION=$(echo $CURRENT_BRANCH | cut -d'-' -f3- | tr '-' ' ')

echo "📋 Issue ID: $ISSUE_ID"
echo "📝 Description: $DESCRIPTION"

# Check for required documentation
HOTFIX_DOC=".hotfix_docs/HOTFIX_${ISSUE_ID}.md"
if [ ! -f "$HOTFIX_DOC" ]; then
    echo "❌ ERROR: Hotfix documentation missing: $HOTFIX_DOC"
    echo "Run git-create-hotfix.mdc first to set up proper documentation"
    exit 1
fi

# Check for review completion
REVIEW_REPORT=".hotfix_docs/REVIEW_REPORT.md"
if [ ! -f "$REVIEW_REPORT" ]; then
    echo "⚠️  WARNING: Review report not found. Run git-review-hotfix.mdc first"
    echo "Proceeding with commit, but review is recommended"
fi
Final Quality Gates:
# Run final test suite
echo "🧪 Running final test validation..."
npm run test
if [ $? -ne 0 ]; then
    echo "❌ ERROR: Tests failing. Cannot commit hotfix with failing tests."
    exit 1
fi

# Check build
echo "🔨 Verifying build..."
npm run build
if [ $? -ne 0 ]; then
    echo "❌ ERROR: Build failing. Cannot commit hotfix with build errors."
    exit 1
fi

# Verify no staged changes conflict
if git diff --cached --exit-code > /dev/null; then
    echo "ℹ️  No staged changes detected. Will stage all modified files."
    git add .
fi

echo "✅ Pre-commit validation complete"

Read the full file on GitHub · 617 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 617 lines · 0 tokens per session scan A 93014807b24b

Subscribe to this mod's changes

git-commit-hotfix is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,650 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.