git-branch-release

git-branch-release is a cursor rule for Cursor from oakensoul/nextjs-cursor-prompts. It costs 0 tokens per session (3,360 once invoked), scanned A, original, MIT.

A Git release workflow guide for creating release branches, setting version numbers, merging changes, deploying to production, and closing out a release.

In plain words
What is it for?
Use it to verify release readiness, create and merge release branches, apply version tags, deploy with validation and monitoring, and document the completed release.
Why use it?
It provides a defined sequence for moving prepared changes into production and helps prevent missed checks, incorrect merges, or incomplete cleanup.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/. Also seen: positional $N argument.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./scripts/validate-release-readiness.sh.

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

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

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-branch-release

README.md
[![agentmods](https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-branch-release.svg)](https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/git-branch-release)
Your own site
<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/git-branch-release"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-branch-release.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 3,360 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.1 $0.00000 $0.03360
Opus 5 $0.00000 $0.01680
Sonnet 5 $0.00000 $0.00672
Haiku 4.5 $0.00000 $0.00336

Measured 6d ago against content hash 356d75fb11d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

git-branch-release scanned grade A with 1 finding 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 6d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -f https://myapp.com/health || {
.cursor/prompts/git/git-branch-release.mdc · 512 lines

How it starts

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

Git Release Branch Execution Guide

This prompt handles the execution phase of release workflow - creating release branches, finalizing versions, executing deployments, and managing the complete release lifecycle.

🎯 RELEASE EXECUTION OBJECTIVES:

  1. EXECUTE release branch creation from prepared release plan
  2. FINALIZE version numbers and apply tags properly
  3. MERGE release branches to main and develop following workflow
  4. DEPLOY to production with proper validation and monitoring
  5. COMPLETE release lifecycle with documentation and cleanup

📋 RELEASE EXECUTION PROCESS:

STEP 1: Pre-execution Validation

Release Readiness Verification:
# Verify release preparation completed
echo "Validating release readiness..."

# Check that release plan exists
if [ ! -f "docs/releases/release-v[VERSION]-plan.md" ]; then
  echo "❌ Release plan not found. Run git-prep-release.mdc first"
  exit 1
fi

# Verify develop branch is ready
git checkout develop
git pull origin develop

# Confirm all planned features are merged
git log --oneline --since="1 month ago" | grep -E "(feat|fix|docs):"

# Check CI/CD status
echo "✅ Develop branch ready for release"
Environment and Dependencies Check:
# Verify all dependencies are secure and up to date
npm audit                           # Security audit
npm outdated                       # Check for outdated packages

# Run comprehensive test suite
npm run test:full                  # All tests including integration
npm run test:e2e                   # End-to-end tests
npm run test:accessibility         # A11y compliance tests

# Verify build process
npm run build                      # Production build
npm run build:analysis            # Bundle analysis

echo "✅ All quality gates passed"

STEP 2: Release Branch Creation and Configuration

Release Branch Creation:
# Set release variables
RELEASE_VERSION="[VERSION]"  # e.g., "1.2.0"
RELEASE_BRANCH="release/v$RELEASE_VERSION"
CURRENT_DATE=$(date +%Y-%m-%d)

echo "Creating release branch: $RELEASE_BRANCH"

# Create release branch from develop
git checkout develop
git pull origin develop
git checkout -b $RELEASE_BRANCH

# Push release branch to remote
git push -u origin $RELEASE_BRANCH

echo "✅ Release branch $RELEASE_BRANCH created"

Read the full file on GitHub · 512 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. 6d ago First seen · 512 lines · 0 tokens per session scan A 356d75fb11d6

Subscribe to this mod's changes

git-branch-release 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 3,360 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.