agentleFS
jamiebrynes7jamiebrynes7/obsidian-todoist-plugin/.claude/skills/write-git-commit/SKILL.md

write-git-commit

Skill1.2k starsChanged 10 months agoMITView on GitHub

Create a git commit following repository conventions

Trending

Quiet since May.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 1 mentionFeb 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: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the jamiebrynes7/obsidian-todoist-plugin 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.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    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:

    Create git commits following the repository's established conventions.

    line 8
  2. Distinctive:

    Use lowercase after the colon

    line 34
  3. Distinctive:

    Use imperative mood ("add feature" not "added feature")

    line 35
  4. Distinctive:

    No period at the end

    line 36
  5. Distinctive:

    Keep concise (ideally under 72 characters total)

    line 37
  6. Distinctive:

    Use sparingly - only when the subject isn't self-explanatory

    line 50
  7. Distinctive:

    DO NOT add Claude as a coauthor to the commit.

    line 61
  8. Distinctive:

    Run git status to see staged and unstaged changes

    line 65
  9. Distinctive:

    Run git diff --staged to review what will be committed

    line 66
  10. Distinctive:

    Write a clear, concise subject line

    line 69
  11. Distinctive:

    Add a body only if the "why" isn't obvious

    line 70

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill 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
SKILL.md

Git Commit

Create git commits following the repository's established conventions.

Commit Message Format

<scope>: <subject>

[optional body]

Scope

The scope indicates which part of the codebase is affected:

  • plugin - Plugin source code changes (most common)
  • docs - Documentation changes
  • scripts - Build/release script changes
  • .github - GitHub workflows and actions
  • .claude - Claude configuration and skills
  • .vscode - VS Code settings
  • * - Changes spanning multiple packages/areas

For focused changes within a scope, you may use a more specific prefix like plugin api, plugin settings, etc.

Subject Line

  • Use lowercase after the colon
  • Use imperative mood ("add feature" not "added feature")
  • No period at the end
  • Keep concise (ideally under 72 characters total)

Examples:

  • plugin: add support for task filtering
  • docs: update query-blocks documentation
  • *: bump versions across the board
  • .github: add separate build job

Body (Optional)

  • Separate from subject with a blank line
  • Explain why the change was made, not what
  • Use sparingly - only when the subject isn't self-explanatory

Example:

plugin: restore react & react-dom dedupe

While the tests pass after aligning react versions between docs/ and
plugin/, the build still breaks at runtime without this.

DO NOT add Claude as a coauthor to the commit.

Process

  1. Run git status to see staged and unstaged changes
  2. Run git diff --staged to review what will be committed
  3. Stage files with git add <files> (prefer specific files over git add -A)
  4. Determine the appropriate scope based on changed files
  5. Write a clear, concise subject line
  6. Add a body only if the "why" isn't obvious
  7. Create the commit

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.