pre-commit-validation SKILL.md skillA
pre-commit-validation from ensodynamics/enso-method is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ensodynamics/enso-method/pre-commit-validation@git:20261028.fdb0982Pins git:20261028.fdb0982 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ensodynamics/enso-method
- Path
skills/pre-commit-validation/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261028.fdb0982, committed Oct 28, 2026
- First version recorded
- Oct 13, 2026
- Size
- 19,730 bytes
- Repository stars
- 6
- License
- MIT
Commit-boundary validation ("git police") — verify the staged changeset is clean, coherent, and safe on a shared multi-session workstation. Expected-changeset staging hygiene, secrets scan, diff sanity, concurrent-commit detection, and committing on the local branch (never building on the remote and pushing around it). Loaded by the implement skills at commit time, before presenting or creating any commit.
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
# Pre-Commit Validation ("Git Police")
## Metadata
- **Type:** reference (loaded by the implement skills at commit time)
- **Trigger:** Follow these guidelines at the commit boundary — after testing, deliverable review and test hardening, before committing
- **Purpose:** Ensure the staged changeset is clean, coherent, and safe — especially important on a shared workstation with concurrent sessions
---
## Why This Exists
This runs in a checkout where several agent sessions (Claude Code, Codex or others), manual edits, and other development work can happen concurrently in the same repo and branch. Files can appear in the staging area or working tree from unrelated work at any moment. Another session can commit to the same branch while you're validating. The autonomous workflow cannot assume that everything visible in `git status` belongs to it, or that the branch state is stable.
…Read the whole file at its exact version.
How to install
mdr add ensodynamics/enso-method/pre-commit-validation@sha256:65945826438c38abThe line at the top of this page pins the label git:20261028.fdb0982, 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_ef22zsgsxjkmm3jk)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Oct 13, 2026 and Oct 28, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.fdb0982 latest | 2026-10-28 | fdb0982 | 19,730 B | A | view · diff |
| git:20261026.9ffab64 | 2026-10-26 | 9ffab64 | 19,641 B | A | view · diff |
| git:20261021.19f2a12 | 2026-10-21 | 19f2a12 | 19,632 B | A | view · diff |
| git:20261019.a149e63 | 2026-10-19 | a149e63 | 19,691 B | A | view · diff |
| git:20261018.9c89f88 | 2026-10-18 | 9c89f88 | 19,497 B | A | view · diff |
| git:20261013.ce3c32b | 2026-10-13 | ce3c32b | 18,332 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 (19730 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
ensodynamics/enso-method · 6 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ef22zsgsxjkmm3jk GET https://markdownregistry.com/api/v1/resolve?ref=ensodynamics/enso-method/pre-commit-validation GET https://markdownregistry.com/api/v1/blob/65945826438c38ab0541c14b11aa029e11bca2429fed275b86cad66bda75c7d8
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.