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
Who's talking about ifer47/markeron
- ScoopInstaller/Scoop“[Bug] checkver github mode not working for url ending with #/dl.7z”GitHub · Jul 14, 2026
- ScoopInstaller/Extras“[Request]: MarkerOn”GitHub · Jul 14, 2026
The biggest 2 of 2 mentions linking to the repository that our crawl found. Each line is their own headline.
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,243 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/cross-platform-ui-styles.mdcCursor rule
- .cursor/rules/i18n.mdcCursor rule
- .cursor/rules/node-toolchain.mdcCursor rule
- .cursor/rules/release-workflow.mdcCursor rule
- cross-platform-tauri-uiSkill
- grill-meSkill
- releaseSkill
- tauri-config-ipcSkill
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
- Distinctive: line 11
Use the interactive prompt — do not hand-write commits unless the user asks:
- Very specific: line 44
Do not: use release: for daily work — npm run release creates chore(release): vX.Y.Z automatically.
- Very specific: line 48
Before commit, ensure staged files pass lint-staged (prettier + oxlint on ts/vue/css).
- Very specific: line 49
If commit-msg hook fails on body length, shorten or remove the body — do not use --no-verify.
≈ “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.
Files
--- 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.
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
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.

