openspec-git-discipline SKILL.md skillA
openspec-git-discipline from intent-driven-dev/intent-driven-template is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add intent-driven-dev/intent-driven-template/openspec-git-discipline@git:20260510.a8b8231Pins git:20260510.a8b8231 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- intent-driven-dev/intent-driven-template
- Path
.agents/skills/openspec-git-discipline/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260510.a8b8231, committed May 10, 2026
- Size
- 2,984 bytes
- Repository stars
- 188
- License
- MIT
Use when running OpenSpec propose, continue, apply, verify, archive, or worktree workflows where proposal artifacts, branches, merges, or archive timing affect git history.
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
# OpenSpec Git Discipline ## Core Rule Every OpenSpec state change must cross `main` before the next lifecycle phase depends on it. - Propose/continue artifacts may be drafted on a branch, but must be committed and merged to `main` before apply starts. - Apply may run on `main`, a branch, or a worktree only if that exact proposal change is already available on `main`. - Archive may run only from `main` after implementation is merged back. Never create commits, branches, or merges unless the user explicitly asks. ## Gates | Moment | Gate | | --- | --- | | Before propose | Prefer `main`; if not, warn and ask whether to continue intentionally. | | During continue | Before creating the next artifact, ask the user to commit completed artifact changes or explicitly continue without that checkpoint. | | After propose | Ask the user to commit proposal artifacts; offer to create a PR branch for review. | | Before apply | Confirm the proposal change is committed on `main`; then apply may run from `main`, a branch, or a worktree. | | Before archive | Stop unless implementation is merged back to `main` and archive is running from `main`. | …
Read the whole file at its exact version.
How to install
mdr add intent-driven-dev/intent-driven-template/openspec-git-discipline@sha256:a5d5bcbfaaa9441cThe line at the top of this page pins the label git:20260510.a8b8231, 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_pcomr34srunyx3yi)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 10, 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 (2984 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
intent-driven-dev/intent-driven-template · 188 stars · license MIT · pushed 2026-10-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pcomr34srunyx3yi GET https://markdownregistry.com/api/v1/resolve?ref=intent-driven-dev/intent-driven-template/openspec-git-discipline GET https://markdownregistry.com/api/v1/blob/a5d5bcbfaaa9441c4b950d23b5a636f85a05aada5cd1fc2add10155c3f241ad5
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.