agentleFS
ifer47ifer47/markeron/.cursor/rules/commit-conventions.mdc

markeron / rules

Cursor rule1.2k starsChanged 5 months agoMITView on GitHub

Conventional Commits for MarkerOn — use npm run commit; body line length and types feed release notes.

Trending

Quiet since July.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 2 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the ifer47/markeron repository that our weekly crawl found: only 2 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Who's talking about ifer47/markeron

The biggest 2 of 2 mentions linking to the repository that our crawl found. Each line is their own headline.

The file

We split this commit-conventions.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
  1. Distinctive:

    Use the interactive prompt — do not hand-write commits unless the user asks:

    line 11
  2. Very specific:

    Do not: use release: for daily work — npm run release creates chore(release): vX.Y.Z automatically.

    line 44
  3. Very specific:

    Before commit, ensure staged files pass lint-staged (prettier + oxlint on ts/vue/css).

    line 48
  4. Very specific:

    If commit-msg hook fails on body length, shorten or remove the body — do not use --no-verify.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 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-conventions.mdc
---
description: Conventional Commits for MarkerOn — use npm run commit; body line length and types feed release notes.
globs: commitlint.config.js,.husky/**,CONTRIBUTING.md
alwaysApply: false
---

# Commit Conventions

## Preferred workflow

Use the interactive prompt — do **not** hand-write commits unless the user asks:

```bash
npm run commit   # czg — pick type, scope, subject
```

Hooks run automatically: `lint-staged` (pre-commit), `commitlint` (commit-msg).

## Format

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

<body optional>
```

| Rule | Limit |
|------|-------|
| Subject | ≤ 100 chars (`subject-max-length`) |
| Body lines | ≤ 100 chars each (`body-max-line-length`) — **split long lines** |

## Types (release notes mapping)

| Type | Release section | When to use |
|------|-----------------|-------------|
| `feat` | ✨ New | User-facing feature |
| `fix`, `hotfix` | 🛠 Fixes | Bug fix |
| `docs` | 📚 Documentation | README, CONTRIBUTING |
| `ci`, `build` | 👷 CI | Workflows, build scripts |
| `ui` | 🧹 Improvements | Visual-only (also valid) |
| `i18n` | 🧹 Improvements | Locale strings |
| `chore`, `refactor`, `perf`, `test`, `style` | 🧹 Improvements | Internal / maintenance |

**Do not** use `release:` for daily work — `npm run release` creates `chore(release): vX.Y.Z` automatically.

## Agent rules

- Before commit, ensure staged files pass `lint-staged` (prettier + oxlint on ts/vue/css).
- If commit-msg hook fails on body length, shorten or remove the body — do not use `--no-verify`.
- Match repo style: lowercase type, imperative subject, no trailing period on subject.
- UI/cross-platform fixes: prefer `fix(ui):` or `ui:` over generic `fix:` when accurate.

See `.cursor/skills/release/SKILL.md` for how commits become release notes.

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.