agentleFS
finograficfinografic/ai-agent-config/.cursor/rules/git-operations.mdc

ai-agent-config / rules

Cursor rule0 starsChanged 3 months agoMITView on GitHub

Mandatory git commit, push, and release policy — read git-policy before acting

  • Commits and pushes

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this git-operations.mdc into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before any commit, push, tag, or release-related action: read and follow .agents/instructions/git/git-policy.instructions.md.

    line 8
  2. Distinctive:

    Only commit when the user explicitly asks

    line 17
  3. Distinctive:

    Do not git push unless the user explicitly asks in the current message

    line 21
  4. Distinctive:

    Do not create remote branches or worktrees unless asked

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
git-operations.mdc
---
description: Mandatory git commit, push, and release policy — read git-policy before acting
alwaysApply: true
---

# Git operations (agents)

**Before any commit, push, tag, or release-related action:** read and follow `.agents/instructions/git/git-policy.instructions.md`.

## Commits (checklist)

- Subject: conventional `type(scope): subject` (allowed types in `commitlint.config.mjs`)
- Body: terse `-` bullet points only — not prose paragraphs
- Multiline messages: `git commit -F <message-file>` (not inline `-m` heredocs)
- Optional `Verification:` section with short bullets
- **Never** `Co-Authored-By`
- Only commit when the user explicitly asks

## Push / remote

- Do not `git push` unless the user explicitly asks in the current message
- Do not create remote branches or worktrees unless asked

## Releases

Human-only — see git-policy for the full deny list. Clarify ambiguous requests (e.g. "ship it") before acting.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.