agentleFS
VenipaVenipa/ytmdesktop2/.cursor/rules/commit.mdc

ytmdesktop2 / rules

Cursor rule1.1k starsChanged 42 days agoCC0-1.0View on GitHub

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the Venipa/ytmdesktop2 repository that our weekly crawl found: only 4 in all, so this is a hint, not a trend. There is no adoption data for this file yet.
  • 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 repository2 other files it gives its agents.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

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

    Use the common format for commit messages: "type(scope): description"

    line 8
  2. Distinctive:

    Don't use scope if it's not necessary.

    line 9
  3. Distinctive:

    Only use lowercase letters in the entire body of the commit message.

    line 10
  4. Distinctive:

    test: A test change (optional.

    line 16
  5. Distinctive:

    Keep it short and to the point, max 50 characters

    line 20
  6. Distinctive:

    Do not write "closes #n", "fixes #n", or a long body that restates the ticket

    line 23
  7. Distinctive:

    Add a detailed description of the commit, max 60 characters (if necessary, add more details in the body, not in the subject, only if a …

    line 39
  8. Distinctive:

    if the commit is signed off, add the Signed-off-by: <username>

    line 45

≈ “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.mdc
---
alwaysApply: true
---
# Commit Messages Guidelines

## Commit Messages

- Use the common format for commit messages: "type(scope): description"
  - Don't use scope if it's not necessary.
- Only use lowercase letters in the entire body of the commit message.
- The type can be one of the following:
  - feat: A new feature
  - fix: A bug fix
  - chore: A chore (non-code change)
  - refactor: A code refactor (optional; only use if it's a significant refactor)
  - test: A test change (optional; only use if it's a significant test change or new test added)
  - docs: Documentation changes
  - style: Code style changes (optional; only use if it's a significant style change)
  - perf: Performance improvements (optional; only use if it's a significant performance improvement)
- Keep it short and to the point, max 50 characters
- Reference GitHub issues/PRs in the subject as `type(#n):`, not in a footer
  - Compact human summary after the colon (what broke / what changed)
  - Do not write "closes #n", "fixes #n", or a long body that restates the ticket
  - Example: "fix(#259): keep ytm fetch bound to networkmanager"
  - Example: "feat(#254): word-driven lyrics fill and auto-open tab"
  - Example: "fix: fixed issue with login"
  - Example: "feat: added new timer feature to the reports page"
  - Example: "feat: updated layout in timer page"
  - Example: "chore: updated dependencies"
  - Example: "refactor: refactored code in timer page - improved performance and readability, reduced code complexity, extended with new features"
  - Example: "test: added new test for timer page"
  - Example: "docs: updated documentation for timer page"
  - Example: "style: updated code style in timer page"
  - Example: "perf: improved performance of timer page"


## Commit Body

- Add a detailed description of the commit, max 60 characters (if necessary, add more details in the body, not in the subject, only if a significant change is made)


## Commit Footer

- Issue/PR numbers belong in the subject (`type(#n):`), not here
- if the commit is signed off, add the Signed-off-by: <username>
  - otherwise leave empty


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.