Context diff
Check which @context annotations are affected by recent code changes. Use after editing code to verify context accuracy and flag stale annotations.From its SKILL.md
npx -y skills add recallnet/codecontext --skill context-diffAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.8 KB, 120 tokens by cl100k_base, as published. Nobody here has run it
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:
- Check if the annotation still accurately describes the code.
- If accurate, recommend bumping
[verified:YYYY-MM-DD]to today's date. - If no longer accurate, recommend updating the annotation summary.
- If the annotated code was removed, recommend removing the annotation.
Flag any !critical annotations that changed — these require careful review.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.