git-commits Cursor ruleA
git-commits from robosushie/brix is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add robosushie/brix/.cursor/rules/git-commits.mdc@git:20261030.e1f81ddPins git:20261030.e1f81dd in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- robosushie/brix
- Path
.cursor/rules/git-commits.mdc- Versions recorded
- 1
- Latest version
- git:20261030.e1f81dd, committed Oct 30, 2026
- Size
- 966 bytes
- Repository stars
- 6
- License
- MIT
Conventional commit messages that pass the local commit-msg hook.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Git commits Only commit when the user asks. A pull request title uses the same first line. Line 1 is exactly: `<type>(optional-scope): <subject>` Types: `feat` | `fix` | `refactor` | `chore` | `docs` | `test` | `style` The subject is only the text after the colon. - Start it with a lowercase letter. Write "add", not "Add". - 72 characters or fewer. - Do not end it with a period. - Imperative verb. - One logical change. Pass the message via HEREDOC. - No `--no-verify`, and no amend of a pushed commit, unless the user asks. If more detail is needed, leave one blank line, then a body that says why. Never put the body on line 1. Good: ```text feat(ci): add semantic commit check The commit-msg hook rejects subjects that do not match this format. ``` Bad: ```text feat: Add a husky hook so generated commit messages follow the repo format. ```
Read the whole file at its exact version.
How to install
mdr add robosushie/brix/.cursor/rules/git-commits.mdc@sha256:f3e6eb2c16385bfbThe line at the top of this page pins the label git:20261030.e1f81dd, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_q2fezmalotpgkp4h)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 30, 2026.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (966 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
robosushie/brix · 6 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_q2fezmalotpgkp4h GET https://markdownregistry.com/api/v1/resolve?ref=robosushie/brix/.cursor/rules/git-commits.mdc GET https://markdownregistry.com/api/v1/blob/f3e6eb2c16385bfbfce93ab9dfadc43ab9d3af2dce25091fadefd4d3ba447353
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: Cursor rules vs AGENTS.md · which agent file does what.