Cursor rule
.cursor/rules/011-conventional-commits.mdcUse when user asks to commit
Cursor rules
Quality
45/100
Scores the file, not the repository.Length
301 words
4 headings · 1 code blocksRepository
1
— · pushed 196 days agoLast changed
3 days ago
First indexed 3 days ago.12345# Conventional Commits67When committing changes, use the Conventional Commit Messages specification:89```10<type>[optional scope]: <description>1112[optional body]1314[optional footer(s)]15```1617## Common Types1819- `feat`: New feature20- `fix`: Bug fix21- `docs`: Documentation changes22- `refactor`: Code refactoring23- `chore`: Maintenance tasks24- `style`: Code style changes (formatting, etc.)2526## Examples2728- `feat(docker): add tdarr service`29- `fix(scripts): correct user group setup`30- `docs: update README with service ports`31- `refactor: move Python scripts to scripts/ directory`3233## Specification Details3435The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.3637- Commits MUST be prefixed with a type, which consists of a noun, feat, fix, etc., followed by the OPTIONAL scope, OPTIONAL !, and REQUIRED terminal colon and space.38- The type `feat` MUST be used when a commit adds a new feature to your application or library.39- The type `fix` MUST be used when a commit represents a bug fix for your application.40- A scope MAY be provided after a type. A scope MUST consist of a noun describing a section of the codebase surrounded by parenthesis, e.g., `fix(parser):`41- A description MUST immediately follow the colon and space after the type/scope prefix. The description is a short summary of the code changes.42- A longer commit body MAY be provided after the short description, providing additional contextual information about the code changes. The body MUST begin one blank line after the description.43- Breaking changes MUST be indicated in the type/scope prefix of a commit, or as an entry in the footer.44- If included as a footer, a breaking change MUST consist of the uppercase text BREAKING CHANGE, followed by a colon, space, and description.45
Also in stvmachine/arr-config
Diff this repo’s formatsOne repository carrying more than one format is the comparison this product exists for: does anyone actually write different content in each file, or is one a copy of the other?
| Repository | Format | Stack | Covers | Score | Changed |
|---|---|---|---|---|---|
| stvmachine/arr-config.cursor/rules/010-workflow.mdc · 1 | Cursor rules | gitdo-notagent-behaviour | 46/100 | 3 days ago | |
| stvmachine/arr-config.cursor/rules/012-minimal-code-changes.mdc · 1 | Cursor rules | no sections | 4/100 | 3 days ago | |
| stvmachine/arr-config.cursor/rules/030-bug-handling.mdc · 1 | Cursor rules | no sections | 16/100 | 3 days ago | |
| stvmachine/arr-config.cursor/rules/040-python-style.mdc · 1 | Cursor rules | style | 20/100 | 3 days ago | |
| stvmachine/arr-config.cursor/rules/050-docker-compose.mdc · 1 | Cursor rules | no sections | 16/100 | 3 days ago | |
| stvmachine/arr-config.cursor/rules/070-best-practices.mdc · 1 | Cursor rules | stylesecuritydo-not | 27/100 | 3 days ago | |
| stvmachine/arr-config.cursor/rules/080-common-tasks.mdc · 1 | Cursor rules | no sections | 25/100 | 3 days ago | |
| stvmachine/arr-config.cursor/rules/999-mdc-format.mdc · 1 | Cursor rules | lint-formatstylearchdo-not+1 | 73/100 | 3 days ago |
Diff against .cursor/rules/010-workflow.mdc Diff against .cursor/rules/012-minimal-code-changes.mdc Diff against .cursor/rules/030-bug-handling.mdc Diff against .cursor/rules/040-python-style.mdc Diff against .cursor/rules/050-docker-compose.mdc Diff against .cursor/rules/070-best-practices.mdc Diff against .cursor/rules/080-common-tasks.mdc Diff against .cursor/rules/999-mdc-format.mdc
Similar configs
Same format, overlapping stack, ranked by quality.
| Repository | Format | Stack | Covers | Score | Changed |
|---|---|---|---|---|---|
| TechSquidTV/Hermes.cursor/rules/10-hermes-api.mdc · 45 | Cursor rules | testlint-formatstylearch+5 | 100/100 | 3 days ago | |
| hiromaily/go-crypto-wallet.cursor/rules/typescript.mdc · 126 | Cursor rules | setupbuildtestlint-format+6 | 100/100 | 3 days ago | |
| langflow-ai/langflow.cursor/rules/docs_development.mdc · 153k | Cursor rules | setupbuildtestlint-format+7 | 97/100 | 3 days ago | |
| TechSquidTV/Hermes.cursor/rules/20-hermes-api-tests.mdc · 45 | Cursor rules | teststyletesting-strategysecurity+3 | 97/100 | 3 days ago | |
| skillrecordings/egghead-next.cursor/rules/project-update-rules.mdc · 1.4k | Cursor rules | buildtestlint-formatstyle+7 | 96/100 | 3 days ago | |
| skillrecordings/egghead-next.cursor/rules/project-update-user-rules.mdc · 1.4k | Cursor rules | buildtestlint-formatstyle+7 | 96/100 | 3 days ago | |
| nerds-odd-e/doughnut.cursor/rules/cli.mdc · 49 | Cursor rules | setupbuildteststyle+4 | 96/100 | 3 days ago | |
| hiromaily/go-crypto-wallet.cursor/rules/proto.mdc · 126 | Cursor rules | buildlint-formatstylearch+3 | 96/100 | 3 days ago |
