deploy-checklist skillA
deploy-checklist is agent-read markdown (skill) from drafthq/draft: Pre-deployment verification checklist. Generates customized checklists based on tech-stack with rollback triggers. Auto-invoked by /draft:upload..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Deploy Checklist You are generating a pre-deployment verification checklist customized to this project's technology stack. ## MANDATORY GRAPH LOOKUP (read before Phase 1) When `draft/graph/schema.yaml` exists, this skill **must** follow the graph-first lookup contract in [core/shared/graph-query.md](../../core/shared/graph-query.md) §Mandatory Lookup Contract. Use the graph to validate module boundaries before the deploy: 1. For each file in the deploy diff, run `"$DRAFT_TOOLS/graph-impact.sh" --repo . --file <path>` to enumerate the modules affected — flag any module **not** declared in `hld.md` §Detailed Design as a deployment-scope miss. 2. Run `"$DRAFT_TOOLS/cycle-detect.sh" --repo .` (and query `"$DRAFT_TOOLS/graph-arch.sh" --repo .` for the module overview) to ensure no fresh cycles were introduced after HLD sign-off. 3. Run `"$DRAFT_TOOLS/hotspot-rank.sh" --repo .` — any hotspot in the diff escalates the Resiliency row of Phase 0. Filesystem `grep` is reserved for source-text scans (migration file names, flag-key strings). Module/impact discovery goes through the graph. ## Red Flags — STOP if you're …
Read the whole file at its exact version.
How to install
mdr add drafthq/draft/deploy-checklist@git:20260819.fda278emdr add drafthq/draft/deploy-checklist@sha256:7231b22bb40757d4Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_yrjlqoetyl2xhw2v)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260819.fda278e latest | 2026-08-19 | fda278e | 12,849 B | A | view · diff |
| git:20260716.8fa8aa0 | 2026-07-16 | 8fa8aa0 | 12,844 B | A | view · diff |
| git:20260616.41b2070 | 2026-06-16 | 41b2070 | 12,822 B | A | view · diff |
| git:20260615.4c8d2a3 | 2026-06-15 | 4c8d2a3 | 12,658 B | A | view · diff |
| git:20260613.740355d | 2026-06-13 | 740355d | 12,639 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 (12849 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
drafthq/draft · 40 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yrjlqoetyl2xhw2v GET https://markdownregistry.com/api/v1/resolve?ref=drafthq/draft/deploy-checklist GET https://markdownregistry.com/api/v1/blob/7231b22bb40757d407428d0867e68dc42938e103dd1a622c4941fe7e3ba2a744
Your agent 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.