git-review-hotfix

git-review-hotfix is a cursor rule for Cursor from oakensoul/nextjs-cursor-prompts. It costs 0 tokens per session (4,134 once invoked), scanned A, original, MIT.

A review checklist for urgent code fixes, or hotfixes, before they are committed and deployed. It checks the fix's scope, tests, documentation, security, performance, monitoring, and rollback preparation.

In plain words
What is it for?
Use it to review a hotfix branch, confirm the change stays within scope, check regression and edge cases, and assess deployment readiness.
Why use it?
It helps catch missing tests, extra changes, incomplete documentation, and deployment risks before a time-sensitive fix reaches users.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it to review a hotfix branch, confirm the change stays within scope, check regression and edge cases, and assess deployment readiness.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/oakensoul/nextjs-cursor-prompts/git-review-hotfix
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.

Clone the repo
git clone --depth 1 https://github.com/oakensoul/nextjs-cursor-prompts

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for git-review-hotfix

README.md
[![agentmods](https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-review-hotfix.svg)](https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/git-review-hotfix)
Your own site
<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/git-review-hotfix"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-review-hotfix.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 4,134 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.04134
Opus 5 $0.00000 $0.02067
Sonnet 5 $0.00000 $0.00827
Haiku 4.5 $0.00000 $0.00413

Measured 8d ago against content hash 8b8ed5aec27a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

git-review-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 8d 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-review-hotfix.mdc · 521 lines

How it starts

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

Hotfix Review and Validation Checklist

This prompt provides comprehensive validation of hotfix implementation ensuring all critical requirements are met before commit and deployment.

🎯 HOTFIX REVIEW OBJECTIVES:

  1. VALIDATE fix implementation meets hotfix standards and scope
  2. VERIFY comprehensive testing including edge cases and regression
  3. CONFIRM documentation is complete and accurate
  4. ASSESS deployment readiness with proper monitoring and rollback plans
  5. ENSURE compliance with security, performance, and business requirements

🔍 HOTFIX IMPLEMENTATION REVIEW:

STEP 1: Fix Scope and Implementation Validation

Hotfix Scope Compliance:
# 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"

# Check commit count since branch creation
COMMIT_COUNT=$(git rev-list --count HEAD ^main)
echo "📊 Commits in hotfix: $COMMIT_COUNT"

if [ $COMMIT_COUNT -gt 5 ]; then
    echo "⚠️  WARNING: High commit count ($COMMIT_COUNT) - ensure minimal scope"
fi
Code Change Analysis:
# Analyze changed files
echo "📁 Files changed in hotfix:"
git diff --name-only main..HEAD

# Show detailed changes
echo "📝 Detailed changes:"
git diff main..HEAD --stat

# Check for large changes
LINES_CHANGED=$(git diff main..HEAD --shortstat | grep -o '[0-9]\+ insertions\|[0-9]\+ deletions' | grep -o '[0-9]\+' | paste -sd+ | bc 2>/dev/null || echo "0")
echo "📊 Total lines changed: $LINES_CHANGED"

if [ $LINES_CHANGED -gt 100 ]; then
    echo "⚠️  WARNING: Large change set ($LINES_CHANGED lines) - validate necessity"
fi
Hotfix Scope Validation Checklist:
  • Minimal changes only - Fix addresses only the critical issue
  • No feature additions - No new functionality introduced
  • No refactoring - Code structure improvements avoided
  • Focused scope - Changes limited to affected components
  • Existing patterns preserved - Current code patterns maintained
  • Configuration minimal - Only essential config changes
  • Documentation proportional - Documentation matches change scope

Read the full file on GitHub · 521 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. 8d ago First seen · 521 lines · 0 tokens per session scan A 8b8ed5aec27a

Subscribe to this mod's changes

git-review-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,134 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.