القائمة
Check which @context annotations are affected by recent code changes. Use after editing code to verify context accuracy and flag stale annotations.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف 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.
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.
Check all staged files for stale @context annotations before committing. Use as a pre-commit verification step.
| name | context-diff |
| description | Check which @context annotations are affected by recent code changes. Use after editing code to verify context accuracy and flag stale annotations. |
| user-invocable | true |
| allowed-tools | Bash(npx codecontext *) |
| argument-hint | <file> |
Run the codecontext diff command on the target file to see which annotations are affected by uncommitted changes.
npx codecontext --diff HEAD $ARGUMENTS
For each affected annotation:
[verified:YYYY-MM-DD] to today's date.Flag any !critical annotations that changed — these require careful review.