@recallnet/codecontext-claude-plugin
Surfaces @context annotations during file reads and edits, giving Claude automatic awareness of project conventions and architectural decisions embedded in c…
Claude Code plugin that automatically surfaces inline @context annotations while Claude reads and edits files, keeping constraints, risks, and past decisions in the loop. Adds three hooks: a read-time reminder that tiers annotations by priority, a pre-edit warning for !critical constraints, and a stop-time staleness check on staged files. Also installs /context-scope, /context-diff, and /context-staged slash commands. For teams that document decisions as inline @context comments.
- Keep Claude aware of important code notes while editing files
- Surface inline documentation automatically during code reviews
- Ensure AI follows your team's code annotation conventions
Surfaces @context annotations during file reads and edits, giving Claude automatic awareness of project conventions and architectural decisions embedded in code comments.
Teams using inline documentation conventions who want Claude to respect existing code context markers during development.
https://github.com/recallnet/codecontext
By GitHub Actions
How to Get It
npm install @recallnet/codecontext-claude-plugin && claude --plugin-dir ./node_modules/@recallnet/codecontext-claude-plugin
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
After installing, paste this into Claude:
Help me keep Claude aware of important code notes while editing files
Trust Signals Auto-scanned
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 5 GitHub stars; 4 contributors; last commit 74d ago; license MIT.
Things to check
- Requires developers to consistently author @context annotations upstream; plugin is only as useful as annotation discipline. Coverage gaps leave engineers without context exactly when they need it.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 5 GitHub stars; 4 contributors; last commit 74d ago; license MIT.