agentleFS
Seriora-ResearchSeriora-Research/seri-agent/.cursor/rules/git-workflow.mdc

seri-agent / rules

Cursor rule0 starsChanged 2 months agoApache-2.0View on GitHub

Feature branches and PRs against dev, never a direct push to main or dev.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Do not push to main or dev.

    line 9
  2. Very specific:

    When the work is verified, push the branch and open a PR with --base dev.

    line 12
  3. Distinctive:

    Do not merge the PR. Hand off after it is open.

    line 19
  4. Very specific:

    Default in-session review is pstack /interrogate (and /no-comments before the PR).

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 6,873 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: Feature branches and PRs against dev, never a direct push to main or dev.
alwaysApply: true
---

# Git workflow

Trunk is `dev`. New work lands via a feature branch and a pull request against `dev`.
Do not push to `main` or `dev`. Do not open a PR that targets `main`. `main` is the
release line.

When the work is verified, push the branch and open a PR with `--base dev`. Do not
fast-forward local `dev` or `main` and push it.

Feature and bugfix work is pstack (`/poteto-mode`), including Opening a PR. Gates
still run. Default review is `/interrogate` + `/no-comments`, plus `/blast-radius`
before the PR. Thermo-nuclear is on-demand.

Do not merge the PR. Hand off after it is open.

Branch names: a descriptive slug (e.g. `feat/<slug>`).

## PR review

Default in-session review is pstack `/interrogate` (and `/no-comments` before the PR).
`/code-review` is user-triggered. Thermo-nuclear is user-triggered.

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.