What is git-code-push?

A checklist for validating code before pushing commits to GitHub. It covers formatting, linting, TypeScript type checks, security, performance, deployment risk, and compatibility with automated pipelines.

Use it to run quality gates, verify production readiness, check GitHub and CI/CD compatibility, and decide whether a push is safe.

It helps prevent failing checks, broken builds, security problems, and unready changes from reaching the shared repository or deployment process.

git-code-push — Cursor rule for Cursor by oakensoul

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-code-push/github.svg)](https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/git-code-push)

Your own site

<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/git-code-push"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-code-push/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/git-code-push"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/git-code-push.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 2,688 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.02688
Opus 5.5	$0.00000	$0.01075
Sonnet 5.5	$0.00000	$0.00538
Haiku 4.5	$0.00000	$0.00269

Measured 1mo ago against content hash 14b6c25fae62, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-code-push 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 1mo 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-code-push.mdc · 330 lines

How it starts

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

Git Code Push Validation Guide

This prompt ensures comprehensive quality validation and production readiness before pushing commits to GitHub. ALL quality gates must pass before proceeding.

🎯 PUSH VALIDATION OBJECTIVES:

EXECUTE comprehensive quality gates with zero tolerance for failures
VALIDATE production readiness including security and performance
VERIFY GitHub integration and CI/CD pipeline compatibility
ASSESS deployment risk and rollback preparedness
AUTHORIZE push execution only after all criteria are met

📋 COMPREHENSIVE VALIDATION PROCESS:

STEP 1: Code Quality Validation

Linting and Formatting Validation:

# Comprehensive code quality checks
npm run lint                 # ESLint validation with zero warnings
npm run lint:fix            # Auto-fix what can be fixed
npm run format              # Prettier formatting validation
npm run type-check          # TypeScript strict type checking

Code Quality Gates:

ESLint clean - Zero errors, zero warnings tolerated
TypeScript strict - No type errors, proper interface usage
Prettier compliant - Consistent code formatting
Import organization - Clean import structure, no unused imports
Dead code elimination - No unreachable or unused code

STEP 2: Testing Validation

Comprehensive Test Suite Execution:

# Full testing pipeline
npm run test                 # Complete unit test suite
npm run test:coverage        # Coverage verification (>80% required)
npm run test:integration     # Integration test validation
npm run test:e2e            # End-to-end test execution (if available)
npm run test:accessibility  # Accessibility compliance testing

Testing Quality Gates:

Unit tests: 100% pass rate - No failing or skipped tests
Coverage threshold met - Minimum 80% code coverage
Integration tests pass - All integration scenarios validated
E2E tests pass - Critical user journeys function correctly
Accessibility tests pass - WCAG compliance verified
Performance tests pass - No performance regressions detected

Read the full file on GitHub · 330 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.

1mo ago First seen · 330 lines · 0 tokens per session scan A 14b6c25fae62

Subscribe to this mod's changes

git-code-push 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 2,688 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.

Git and workflow

git-code-push