pahlevikunpahlevikun/levistack/.cursor/rules/git-workflow.mdc

levistack / rules

Cursor rule0 starsChanged 18 days agoMITView on GitHub

Work in one checkout on one branch; no git worktrees; commit only when asked; run local gates before pushing.

Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,183 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository57 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/comments.mdcCursor rule
- .cursor/rules/commit-messages.mdcCursor rule
- .cursor/rules/manage-stack.mdcCursor rule
- .cursor/rules/no-worktrees.mdcCursor rule
- manage-stackSkill
- convert-as-skillSkill
- create-agentSkill
- create-agents-mdSkill
- create-commandSkill
- create-hookSkill
- create-ruleSkill
- create-skillSkill
- retrospectiveSkill
- super-architectureSkill
- super-cachingSkill
- super-elixirSkill
- super-nodejsSkill
- super-protobufSkill
- super-tech-blueprintSkill
- atomic-semantic-commitSkill
- code-reviewSkill
- create-bruno-collectionSkill
- create-documentationSkill
- create-ticketsSkill
- ready-specSkill
- write-adrSkill
- write-changelogSkill
- write-mr-descriptionSkill
- write-planSkill
- write-postmortemSkill
- write-runbookSkill
- noslopSkill
- output-saversSkill
- safe-refactorSkill
- tddSkill
- verifySkill
- get-movingSkill
- later-listSkill
- standupSkill
- challenge-meSkill
- codebase-learnerSkill
- researchSkill
- second-opinionSkill
- traceSkill
- color-kitSkill
- design-system-kitSkill
- diagramSkill
- infographicSkill
- product-polish-workflowSkill
- prototype-wireframeSkill
- ui-ux-kitSkill
- evidenceSkill
- find-skillsSkill
- handoffSkill
- rumblingSkill
- use-levistackSkill

The file

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

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Use one working tree on the current branch, or a short-lived feature branch checked out in the repo root.
line 8
Distinctive:
Commit and merge or rebase before starting unrelated work.
line 11
Distinctive:
Commit only when the user asks.
line 12
Very specific:
Update the changelog under an Unreleased heading for user-facing changes, when the repo keeps one.
line 13
Distinctive:
Never commit generated artifacts such as coverage output, build products or local caches.
line 15
Distinctive:
Run the repository's normal gate (format, lint, type check, tests) and git status to confirm no stray artifacts are staged.
line 18

≈ “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-workflow.mdc

---
description: "Work in one checkout on one branch; no git worktrees; commit only when asked; run local gates before pushing."
alwaysApply: true
---

# Git workflow

- Use **one working tree** on the current branch, or a short-lived feature branch checked out in the repo root. Never use worktrees; see `no-worktrees.mdc`.
- For parallel work, run background agents in the same tree on disjoint file sets.
- For a risky change, use a feature branch in the same checkout, not an extra worktree.
- Commit and merge or rebase before starting unrelated work. Stash or commit WIP when switching tasks.
- Commit only when the user asks. Do not push unless explicitly requested.
- Update the changelog under an `Unreleased` heading for user-facing changes, when the repo keeps one.
- **Preserve unrelated changes.** Other work may be in the tree. Do not initialize, stage, amend, rewrite, discard, branch, release or deploy without explicit authorization, and keep a requested commit focused.
- Never commit generated artifacts such as coverage output, build products or local caches.

## Before pushing
Run the repository's normal gate (format, lint, type check, tests) and `git status` to confirm no stray artifacts are staged. Report any gate you could not run.

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.

Check your setup, free