commit SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 4 indexed copies. Same content hash, so the same checks give both the same grade.
commit from yelmuratoff/agent_sync is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yelmuratoff/agent_sync/commit@git:20260728.7c60c81Pins git:20260728.7c60c81 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yelmuratoff/agent_sync
- Path
.ai/src/skills/commit/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260728.7c60c81, committed Jul 28, 2026
- First version recorded
- Apr 25, 2026
- Size
- 2,370 bytes
- Repository stars
- 17
- License
- GPL-3.0
Create a well-structured git commit for staged or unstaged changes — analyze the diff, match the project's existing commit style, write a clear message, and create the commit. Use this skill when the user asks to commit, save changes, check in code, write a commit message, prepare changes for push, or wrap up a piece of work — even when they don't say "commit" explicitly (e.g. "let's save this", "ship it", "save the changes").
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Commit Write a commit message that follows the project's conventions and clearly explains what changed and why. ## Steps 1. Run `git diff --cached` (or `git diff` if nothing is staged) to see all changes. 2. Run `git log --oneline -10` to detect the project's existing commit style — copy it. Match what's there rather than imposing a different convention. 3. Analyze the changes: feature, fix, refactor, docs, or chore? What is the *motivation*? 4. Write the commit: - **First line**: imperative mood, ≤72 chars, matching the style from step 2. - **Body** (only if the subject can't carry the meaning): blank line, then *why*, not *what*. 5. Stage relevant files explicitly by path. `git add .` sweeps in generated files, secrets, and unrelated changes. 6. Create the commit. ## Default style If the project has no established convention (step 2 returns mixed messages), default to **Conventional Commits**: `<type>: <subject>` where `<type>` is `feat`, `fix`, `refactor`, `docs`, `test`, or `chore`. Use `feat:` for new behavior, `fix:` for bug fixes, `refactor:` for behavior-preserving changes; the others are self-explanatory. ## Gotchas …
Read the whole file at its exact version.
How to install
mdr add yelmuratoff/agent_sync/commit@sha256:f1c69585d1a7d0acThe line at the top of this page pins the label git:20260728.7c60c81, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ffhoiuew265igymp)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 25, 2026 and Jul 28, 2026, about one every 24 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260728.7c60c81 latest | 2026-07-28 | 7c60c81 | 2,370 B | A | view · diff |
| git:20260603.16f060c | 2026-06-03 | 16f060c | 2,387 B | A | view · diff |
| git:20260512.459bec7 | 2026-05-12 | 459bec7 | 2,208 B | A | view · diff |
| git:20260512.5fd702f | 2026-05-12 | 5fd702f | 2,101 B | A | view · diff |
| git:20260425.aadd161 | 2026-04-25 | aadd161 | 2,031 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2370 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yelmuratoff/agent_sync · 17 stars · license GPL-3.0 · pushed 2026-10-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ffhoiuew265igymp GET https://markdownregistry.com/api/v1/resolve?ref=yelmuratoff/agent_sync/commit GET https://markdownregistry.com/api/v1/blob/f1c69585d1a7d0ac4c1ee8332798748d1e45a4cda99059d09b537ad7246c14e1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from yelmuratoff/agent_sync
Every file in yelmuratoff/agent_sync