emgreppiemgreppi/Business-Central-AI-Skill/writing-git-commits/SKILL.md

writing-git-commits

Skill1 starsChanged 9 months agoMITView on GitHub

Writes git commit messages with proper format, type prefixes (feat/fix/chore), and imperative mood. Use when committing changes, writing a commit message, formatting commit text, or asking how to commit code properly.

1 other project uses a version of this.

Adopted by

Most recently taken up by

DanaResearchGroup/agent-skillstheir own version, first seen Aug 26, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
DanaResearchGroup/agent-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- authenticating-with-oauthSkill
- binding-event-subscribersSkill
- building-cue-rolecentersSkill
- consuming-bc-standard-apiSkill
- controlling-al-accessSkill
- creating-bc-custom-apiSkill
- handling-bc-filesSkill
- implementing-al-interfacesSkill
- implementing-telemetrySkill
- integrating-azure-servicesSkill
- optimizing-bc-performanceSkill

The file

We split this skill into the rules it gives an agent

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

≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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:
Body/Footer: Only if explicitly requested by user
line 14
Distinctive:
Final: No past tense, no generic messages, no file names in subject
line 15
Distinctive:
Do NOT include by default
line 49
Distinctive:
Use past tense ("added", "fixed")
line 98
Distinctive:
Use generic messages ("fix bug", "update code")
line 101

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

Skill: Git Commit Message Rules

Validation Gates

Subject: Type prefix present, imperative mood, max 72 chars
Body/Footer: Only if explicitly requested by user
Final: No past tense, no generic messages, no file names in subject

Basic Rules

Property	Value
Language	English
Subject max	72 characters
Tone	Imperative ("add", "fix", not "added", "fixed")

Allowed Types

Type	Description	Example
`feat`	New features	`feat: add purchase order support`
`fix`	Bug fixes	`fix: resolve user login issue`
`chore`	Non-feature (build, config)	`chore: rename rental file`
`refactor`	Code refactoring	`refactor: simplify rent logic`
`deploy`	Deployment changes	`deploy: trigger deployment`
`docs`	Documentation only	`docs: update starting guide`

Subject Line Format

<type>: <short description in imperative mood>

Examples:

feat: add customer validation on save
fix: correct tax amount calculation
refactor: extract logic to helper codeunit

Body (only if requested)

Do NOT include by default
Explain why and how, not just what
Wrap at ~72–100 chars

feat: add automatic token refresh for API calls

- Tokens cached with expiration tracking
- Auto-refresh 5 minutes before expiry
- Fallback to re-authentication if refresh fails

Footer (only if requested)

BREAKING CHANGE: describe what changed
Issue refs: Refs: #123, Closes: #456

feat: change API endpoint structure

BREAKING CHANGE: API endpoints now require version prefix.
Old: /api/customers → New: /api/v2.0/customers

Refs: #456

Quick Reference

Minimum (default):

feat: add customer export functionality

With body:

feat: add customer export functionality

Implements CSV export with date range filtering.

With footer:

fix: resolve duplicate entry error

Closes: #790

Do NOT

Use past tense ("added", "fixed")
Exceed 72 characters in subject
Include body/footer unless requested
Use generic messages ("fix bug", "update code")
Include file names in subject

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.

Check your setup, free