git-style
Skill1 starsChanged 9 days agoApache-2.0View on GitHub
Prepare focused Git changes and clear commit messages, using Conventional Commits when the project has no other convention. Use when organizing a change, preparing a commit, or discussing Git workflow. Follow project branch and integration rules, and perform commits or remote actions only within the user's authorization.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- approval-gateSkill
- cleanupSkill
- fresh-reviewSkill
- interviewSkill
- no-tombstonesSkill
- orchestrateSkill
- repo-styleSkill
- setupSkill
- task-planSkill
- using-anythingSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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 9
Follow the user's request and applicable project conventions.
- Distinctive: line 21
Keep each commit coherent enough to understand and review on its own.
- Distinctive: line 24
Verify the affected result using the project's applicable checks.
- Distinctive: line 25
Do not fabricate an author, signature, issue reference, or attribution trailer.
- Distinctive: line 31
Use this form by default:
- Distinctive: line 41
Use a short, concrete summary of the change.
- Distinctive: line 46
Add issue references and trailers only when applicable.
- Distinctive: line 58
Commit, push, publish, merge, rewrite history, or delete branches only when authorized for that effect.
- Distinctive: line 62
Verify the actual repository or remote result when an action is performed, then report it accurately.
≈ “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 style
Follow the user's request and applicable project conventions. When no commit-message convention is established, use Conventional Commits 1.0.0.
This skill needs Git only for Git operations. Without repository access, help draft the proposed change or message. Do not initialize a repository or install tools as a side effect.
Understand the state
Inspect the relevant repository status, changes, and recent history when available. Identify the intended scope and existing conventions. Preserve unrelated edits and user work.
Choose branch and integration behavior from the task and project. This skill does not require a feature branch, worktree, merge commit, squash, or pull request.
Prepare focused changes
- Keep each commit coherent enough to understand and review on its own.
- Stage only intended changes, using explicit paths or selected hunks as needed. Do not scoop up unrelated changes.
- Include necessary tests and documentation with the behavior they explain.
- Verify the affected result using the project's applicable checks. Report meaningful limits and unrelated failures.
- Do not fabricate an author, signature, issue reference, or attribution trailer. Use configured identity and required project metadata.
Preparing a change or message does not itself mean the user asked you to commit it.
Write the message
Use this form by default:
<type>[optional scope][!]: <summary>
<optional explanation>
<optional footers>Use a short, concrete summary of the change. Include a scope when it helps identify the affected area. Explain the reason or non-obvious consequence in the body.
featintroduces a feature;fixcorrects a bug.- Other useful types include
docs,refactor,test,perf,build,ci, andchore. Follow the project's type set when it has one. - Mark a breaking change with
!before the colon or aBREAKING CHANGE:footer, and explain the compatibility impact. - Add issue references and trailers only when applicable. Do not treat a local formatting preference as a requirement of the specification.
Examples:
feat(search): filter results by tag
fix(parser): handle an empty input
docs: explain local installationExecute and report
Commit, push, publish, merge, rewrite history, or delete branches only when authorized for that effect. Reuse authorization within its scope; clarify a material change rather than re-asking about the same action. An approval-gate skill can help if installed, but is not required.
Respect protected branches and project integration policy. Avoid rewriting or discarding unrelated work. Cleanup needs its own applicable authorization and ownership check.
Verify the actual repository or remote result when an action is performed, then report it accurately. Do not claim a commit, push, or merge when you only prepared its contents.
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.

