Context scope
Force agents to read critical context left by other agents, enforced by linting and freshness checks.
npx -y skills add recallnet/codecontext --skill context-scopeAssembled 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.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
1.1 KB, 160 tokens by cl100k_base, as published. Nobody here has run it
Run the codecontext scope command on the target file to surface all @context annotations sorted by priority.
npx codecontext --scope $ARGUMENTS
Present the results grouped by priority:
- Critical — MUST read before editing. Violating these risks defects or constraint violations.
- High — SHOULD read. Significantly reduces risk of unintended consequences.
- Normal/Low — Informational context.
If any annotations contain {@link file:.claude/skills/.../SKILL.md} references,
tell the user which skill to load before editing that code.
If annotations have review-required or stale status, flag them and recommend
the user verify or update the [verified:YYYY-MM-DD] date.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.