commit-atomic SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
commit-atomic from jellydn/my-ai-tools is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jellydn/my-ai-tools/commit-atomic@git:20260814.d1987f5Pins git:20260814.d1987f5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jellydn/my-ai-tools
- Path
configs/amp/plugins/my-ai-tools-skills/skills/commit-atomic/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260814.d1987f5, committed Aug 14, 2026
- Size
- 4,246 bytes
- Repository stars
- 128
- License
- MIT
Group staged changes into atomic commits with commitizen convention.
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
# Atomic Commit with Logical Grouping Create atomic commits by logically grouping changes following the commitizen/conventional commits convention. Each commit should represent one logical change with a clear, informative message explaining the **what** and **why**. ## Usage ```bash /commit-atomic ``` ## Process ### 1. Inspect the current changes ```bash git status git diff --staged git diff ``` Review all modified, added, and deleted files to understand the full scope of changes. ### 2. Group changes logically Analyze the changes and group them into **logical, independent units**. Each group should: - Address a single concern or feature - Be independently understandable - Not break the build or tests on its own - Follow the dependency order (low-level to high-level) **Grouping strategies:** - By feature or concern (e.g., authentication, UI, database) - By type (e.g., refactoring, bug fix, new feature) - By layer (e.g., model, service, controller) ### 3. Stage each group intentionally **Stage files explicitly with `git add <path>`.** Avoid `git add -A` or `git add --all`: ```bash # Stage specific files git add <file1> <file2> # Stage specific hunks interactively …
Read the whole file at its exact version.
How to install
mdr add jellydn/my-ai-tools/commit-atomic@sha256:a03bf1fe180fe494The line at the top of this page pins the label git:20260814.d1987f5, 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_p76ro6rqeom6cxjr)
8 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 14, 2026.
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 (4246 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
jellydn/my-ai-tools · 128 stars · license MIT · pushed 2026-11-09 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_p76ro6rqeom6cxjr GET https://markdownregistry.com/api/v1/resolve?ref=jellydn/my-ai-tools/commit-atomic GET https://markdownregistry.com/api/v1/blob/a03bf1fe180fe4943ecc9dd833428d871bae09a5a544f519996661805990740b
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 jellydn/my-ai-tools
Every file in jellydn/my-ai-tools