agentleFS
Sign inStart free
first-flukefirst-fluke/fullstack-starter/.cursor/rules/commit.mdc

fullstack-starter / rules

Cursor rule223 starsChanged 28 days agoMITView on GitHub

Conventional Commits specification and git commit workflow rules

  • Reads credentials

We split this commit.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    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. Distinctive:

    Analyze changes: before committing

    line 23
  2. Distinctive:

    Split by feature: if changes span multiple domains

    line 24
  3. Distinctive:

    Never: use git add -A or git add .

    line 26
  4. Distinctive:

    Never: commit files that may contain secrets (.env, credentials)

    line 27
  5. Distinctive:

    Always: use specific file names when staging

    line 28
  6. Distinctive:

    Do NOT split when: all changes belong to a single feature, few files (5 or fewer)

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 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
commit.mdc
---
description: "Conventional Commits specification and git commit workflow rules"
globs: 
alwaysApply: false
---

<!-- Generated by oh-my-agent. Source: .agents/rules/commit.md -->

# Commit Standards

## Format

```
<type>(<scope>): <description>

[optional body]
```

**Types**: feat, fix, refactor, docs, test, chore, style, perf, build, ci, revert

## Rules

1. **Analyze changes** before committing
2. **Split by feature** if changes span multiple domains
3. **Description** under 72 characters, imperative mood, lowercase, no trailing period
4. **Never** use `git add -A` or `git add .` without explicit permission
5. **Never** commit files that may contain secrets (.env, credentials)
6. **Always** use specific file names when staging
7. Split commits when: different scopes, different types, logically independent changes
8. Do NOT split when: all changes belong to a single feature, few files (5 or fewer)
9. Precedence: logical independence decides first (one logical change = one commit); file count (5 or fewer) is only a tiebreaker; an explicit user instruction overrides both

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