What is git-code-shipit?

A guided Git workflow for reviewing code changes, creating commits, checking quality, and pushing them to GitHub. Git is the tool used to track code history, while GitHub hosts shared code repositories.

Use it to prepare changes, choose how to group commits, update documentation, run checks, push to GitHub, and report the result.

It reduces the chance of committing incomplete, poorly documented, or unsafe changes. It also adds checkpoints before changes are sent to the shared repository.

git-code-shipit — Cursor rule 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.

agentmods

npx agentmods add rules/oakensoul/nextjs-cursor-prompts/git-code-shipit

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 3,021 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.03021
Opus 5	$0.00000	$0.01510
Sonnet 5	$0.00000	$0.00604
Haiku 4.5	$0.00000	$0.00302

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

Security

Grade A, and why

git-code-shipit 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-code-shipit.mdc · 362 lines

How it starts

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

Git Code Ship It - Complete Workflow Orchestrator

🚢 This is the ultimate "Ship It" command - a comprehensive git workflow that takes you from code changes to GitHub push with complete quality validation and documentation.

🎯 SHIP IT OBJECTIVES:

ORCHESTRATE complete git workflow from preparation through push
ENSURE comprehensive quality at every phase with zero tolerance for failures
PROVIDE detailed reporting of all operations and validations
MAINTAIN safety checkpoints with clear go/no-go decisions
DELIVER production-ready code to GitHub with confidence

🚢 SHIP IT WORKFLOW PHASES:

Phase 1: PREPARATION    → Analyze, document, plan
Phase 2: COMMIT         → Validate, execute, verify  
Phase 3: PUSH           → Quality gates, security, deploy
Phase 4: CONFIRMATION   → Success report, monitoring

📋 COMPLETE SHIPIT PROCESS:

🔍 PHASE 1: PREPARATION

Following .cursor/prompts/git/git-code-prep.mdc

Comprehensive Change Analysis:

Analyze all modifications - Files changed, features added, bugs fixed
Determine commit strategy - Single vs. multiple commits, logical grouping
Update documentation - Changelog, README, API docs, sitemap
Plan commit messages - Conventional commit format preparation
Execute initial quality checks - Precommit hooks, linting, type checking

Phase 1 Success Criteria:

Change analysis complete - Full understanding of modifications
Documentation updated - Changelog, LLMs.mdc, sitemap current
Commit strategy planned - Clear execution plan prepared
Initial quality gates pass - Precommit hooks successful
Files staged appropriately - Correct staging for planned commits

🚨 Phase 1 Checkpoint:

CONTINUE TO PHASE 2? [GO/NO-GO]

If NO-GO: Stop, address preparation issues, re-run Phase 1

✅ PHASE 2: COMMIT EXECUTION

Following .cursor/prompts/git/git-code-commit.mdc

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

2d ago First seen · 362 lines · 0 tokens per session scan A a48aa765e2f6

Subscribe to this mod's changes

git-code-shipit 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,021 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 Productivity Writing and docs

git-code-shipit

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Git Code Ship It - Complete Workflow Orchestrator

🎯 SHIP IT OBJECTIVES:

🚢 SHIP IT WORKFLOW PHASES:

📋 COMPLETE SHIPIT PROCESS:

🔍 PHASE 1: PREPARATION

Comprehensive Change Analysis:

Phase 1 Success Criteria:

🚨 Phase 1 Checkpoint:

✅ PHASE 2: COMMIT EXECUTION

What this file has done since we first saw it

Other cursor rules, from other repositories

angular-20

dev-standard

coolify-ai-docs

typescript

python_lib

specs