context-preflight skillA
context-preflight is agent-read markdown (skill) from vmobifystudio/app-dev-team: Run before changing a repository to verify branch, worktree, ticket, dependencies, source-of-truth documents, and unresolved obligations are understood..
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
# Context preflight
Use before implementation, review, migration, release, or any command that can change files. The
purpose is not to create more ceremony; it is to prevent an agent from acting on stale context.
## Procedure
1. Run `node "${CLAUDE_PLUGIN_ROOT}/scripts/context-preflight.mjs" <project-root> [--ticket ID]`.
2. Read the reported branch, dirty-tree, active-worktree, ticket, and required-document findings.
3. Read the ticket, its dependency ancestors, the architecture/engineering-principles docs, the Git
strategy, and the latest relevant decision or follow-up before editing.
4. If the result is `CANNOT EVALUATE`, stop. Do not convert missing context into an assumption.
5. Record assumptions and the next action in the ticket's daily evidence file.
## Operating rules
- A dirty tree belongs to somebody until proven otherwise. Preserve it and ask before overlapping it.
- The current branch and worktree are facts, not suggestions. Never work on `main` when the task writes.
- A ticket is not ready because it is assigned; its dependencies must be merged and its acceptance
criteria must be discoverable.
…Read the whole file at its exact version.
How to install
mdr add vmobifystudio/app-dev-team/context-preflight@git:20260731.42d47b3mdr add vmobifystudio/app-dev-team/context-preflight@sha256:46894320055f92b3Pin 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_hviq4hhemofbzz7d)
1 badge views in 30 days
Versions
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 (1772 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
vmobifystudio/app-dev-team · 4 stars · license MIT · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hviq4hhemofbzz7d GET https://markdownregistry.com/api/v1/resolve?ref=vmobifystudio/app-dev-team/context-preflight GET https://markdownregistry.com/api/v1/blob/46894320055f92b30f7792836b19c346b24a4ee7fe2ea5710e1dc9bc6c12ea1e
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.