agentleFS
hashiiiiihashiiiii/rules-for-ai/skills/hashiiiii-git/SKILL.md

hashiiiii-git

Skill10 starsChanged 3 months agoMITView on GitHub

Use this skill to name a Git branch or write a commit message.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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 same type for the branch name and commit subject.

    line 8
  2. Distinctive:

    Use short English words. Exclude issue numbers, extra prefixes, personal names, and Japanese text from the branch name.

    line 14
  3. Distinctive:

    Write one imperative English line of 50 characters or fewer.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 Conventions

Use the same type for the branch name and commit subject.

Branch

Format: <type>/<short-english-kebab>

Use short English words. Exclude issue numbers, extra prefixes, personal names, and Japanese text from the branch name.

Commit

Format: <type>: <subject>

Write one imperative English line of 50 characters or fewer. Start the subject with a lowercase word and omit the final period.

Types

TypeUse
featAdd a feature or capability.
fixCorrect a defect.
docsChange documentation only.
styleChange formatting or whitespace without changing behavior.
refactorRestructure code without changing behavior.
perfImprove performance.
testAdd or correct tests.
buildChange the build system or dependencies.
ciChange CI files.
choreDo maintenance, such as a .gitignore change.
revertRevert an earlier commit.

Choose the closest type from this list.

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.