conformance-audit 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.
conformance-audit from 0x0w1/jig is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add 0x0w1/jig/conformance-audit@git:20260901.ea92942Pins git:20260901.ea92942 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- 0x0w1/jig
- Path
.claude/skills/conformance-audit/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260901.ea92942, committed Sep 1, 2026
- Size
- 5,827 bytes
- Repository stars
- 5
- License
- MIT
Use to check whether a repository's history actually followed the jig procedure: conventional squash subjects, Release-Grade trailers on unreleased work, version tag format and placement, the main/develop fast-forward invariant, and a committed rubric. Read-only, exits non-zero on violations, and runs in CI.
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
# Conformance Audit Use this repository skill to verify **after the fact** that the procedure was followed. The push guards stop a bad push while it happens; nothing else checks that what did land matches the rules. Three skills look at a repository and none of them overlap: | Skill | Subject | Writes | |---|---|---| | `jig-doctor` | the jig installation | nothing | | `repo-hygiene` | debris in the local clone | deletes what the user names | | `conformance-audit` | the history the procedure produced | nothing | This one never edits, deletes, or rewrites anything. Its output is a report and an exit code. ## Why a Baseline A repository that installs jig today has years of history written under other rules. Judging all of it reports the repository as broken on day one and teaches the user to ignore the tool. Every run therefore starts from a baseline and judges nothing before it: 1. `--since <ref>` when the user names one. 2. The commit that added `.jig/versioning.md` — the point the repository adopted the grading contract. 3. The oldest `vX.Y.Z` tag. 4. Nothing resolves → stop with a usage error. Never fall back to the whole history. …
Read the whole file at its exact version.
How to install
mdr add 0x0w1/jig/conformance-audit@sha256:bc76af7570694d59The line at the top of this page pins the label git:20260901.ea92942, 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_z6ckueq7vgxfbkur)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 1, 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 (5827 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
0x0w1/jig · 5 stars · license MIT · pushed 2026-09-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_z6ckueq7vgxfbkur GET https://markdownregistry.com/api/v1/resolve?ref=0x0w1/jig/conformance-audit GET https://markdownregistry.com/api/v1/blob/bc76af7570694d59f31a15708941deca4414d13a10f52f0167042d76107935fb
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.