hashiiiii-git
Skill10 starsChanged 3 months agoMITView on GitHub
Use this skill to name a Git branch or write a commit message.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hallmarkSkill
- hashiiiii-explain-prSkill
- hashiiiii-imagesSkill
- hashiiiii-issuesSkill
- hashiiiii-localeSkill
- hashiiiii-pull-requestSkill
- hashiiiii-write-enSkill
- hashiiiii-write-jaSkill
- hashiiiii-zigSkill
- show-meSkill
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
- Distinctive: line 8
Use the same type for the branch name and commit subject.
- Distinctive: line 14
Use short English words. Exclude issue numbers, extra prefixes, personal names, and Japanese text from the branch name.
- Distinctive: line 20
Write one imperative English line of 50 characters or fewer.
≈ “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.
Files
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
| Type | Use |
feat | Add a feature or capability. |
fix | Correct a defect. |
docs | Change documentation only. |
style | Change formatting or whitespace without changing behavior. |
refactor | Restructure code without changing behavior. |
perf | Improve performance. |
test | Add or correct tests. |
build | Change the build system or dependencies. |
ci | Change CI files. |
chore | Do maintenance, such as a .gitignore change. |
revert | Revert an earlier commit. |
Choose the closest type from this list.
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
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.

