BrowseFull catalogOutcomesSolve a specific problemRolesStack by teamTrustFilter by risk tier
← Back to the Claude Observatory

@recallnet/codecontext-claude-plugin

Skill Development Usable
Works inClaude Code
Usable Scanned — metadata only

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.

5 starsMIT (commercial OK)FreeQuick setup
Usable rating — This tool is functional but has notable gaps. Review the evaluation notes below before deploying.

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.

Claude Code Claude Cowork Claude Chat

https://github.com/recallnet/codecontext

By GitHub Actions

How to Get It

Option 1: Claude Desktop App (Code Mode)Click the + button next to the prompt box → PluginsAdd plugin. Search and click Install. Skills work in Claude Code only.
Option 2: Paste into Claude CodeCopy the command below and paste it into your conversation. Claude will install it.
Command
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.

First thing to try

After installing, paste this into Claude:

Help me keep Claude aware of important code notes while editing files

Trust Signals Auto-scanned

Stars5Contributors4Last updated2026-04-23LicenseMIT (OK for commercial use)Weekly downloads17Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-08-13 · scanner v1

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

Ease of Use
3/5
Versatility
2/5
Reliability
4/5
Security
3/5
Overall score3.00 / 5.00 UsableEvaluatedJul 2026
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 5 GitHub stars; 4 contributors; last commit 74d ago; license MIT.

← Back to the Claude Observatory

Rolling Claude out in your org? Let's talk.

Start a conversation →