Menu
Check all staged files for stale @context annotations before committing. Use as a pre-commit verification step.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Set up or repair codecontext adoption in a project. Use this whenever the user wants to add @context annotations to a repo, install the codecontext toolchain, update AGENTS.md guidance, improve agent workflows around decision capture, or audit whether an existing codecontext setup is coherent. Prefer this skill over vague "document the tool" work: it is specifically for making a repo actually usable with codecontext.
Check which @context annotations are affected by recent code changes. Use after editing code to verify context accuracy and flag stale annotations.
Surface @context annotations before editing a file. Shows critical constraints, tradeoffs, and risks sorted by priority. Use when about to modify unfamiliar or complex code, or when the user asks what constraints apply to a file.
| name | context-staged |
| description | Check all staged files for stale @context annotations before committing. Use as a pre-commit verification step. |
| user-invocable | true |
| allowed-tools | Bash(npx codecontext *) |
| context | fork |
Run the codecontext staged check across all files in the git staging area.
npx codecontext --staged
If stale annotations are found:
[verified:YYYY-MM-DD] to today if the context is still accurate.If all annotations are fresh, confirm that the staged files are clear to commit.