By biznuts
Keep your project's docs, language, and conventions in sync through the whole session — and surviving auto-compact. Per-project, opt-in via the /never-stale command.
Keep your project's docs, language, and conventions in sync through the whole session — and surviving auto-compact. A Claude Code plugin.
The problem: in a long Claude Code session, the assistant quietly drifts. It forgets to update the docs after a change, forgets which language you wanted, and after an auto-compact it loses the rules you set at the top of the conversation.
never-stale fixes that without you having to repeat yourself. Run one command in a
project and it installs a small, durable setup that keeps the rules in front of the
assistant — including right after every compaction.
Running /never-stale in a project scaffolds three things:
CLAUDE.md — your project rules (auto-loaded every session, survives compaction):
SessionStart (compact) hook — re-injects the rules right after an
auto-compact, so the assistant doesn't "forget" mid-session.PostToolUse (Edit/Write) hook — nudges the assistant to sync docs every
time a file changes.The hooks run via Node (which Claude Code already requires), so the same setup works on Windows, macOS, and Linux — no shell-specific scripts, no encoding pitfalls.
/plugin marketplace add biznuts/never-stale
/plugin install never-stale@never-stale
Then, in any project you want to keep in sync:
/never-stale
It asks your language preferences, scaffolds the files, then asks you to restart
Claude Code so the hooks load. /hooks will show them registered.
| Piece | Mechanism | Why it survives compaction |
|---|---|---|
| Rules | CLAUDE.md | Loaded into context every session, re-injected after compaction |
| Compact reminder | SessionStart hook, matcher compact | Fires right after auto-compact |
| Doc-sync reminder | PostToolUse hook, matcher Edit|Write|MultiEdit | Fires after each file change, emitted as additionalContext JSON |
The reminders point back to CLAUDE.md (the single source of truth), so changing
the language or rules later just means editing that file.
/never-stale command; it does not impose anything on any project automatically.
Run the command where you want it; other projects are untouched.PATH (Claude Code already needs it).MIT — see LICENSE.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub biznuts/never-stale --plugin never-staleMake your AI agent code with your project's architecture, rules, and decisions.
Comprehensive C4 architecture documentation workflow with bottom-up code analysis, component synthesis, container mapping, and context diagram generation
Complete AI coding workflow system. Self-correcting memory + persistent FTS5-indexed research wikis + auto-research loop + multi-LLM council on a single SQLite store. 33 skills, 8 agents, 22 commands, 37 hook scripts across 24 events. Cross-agent via SkillKit.
Create comprehensive documentation for code, APIs, and projects.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Build and maintain an LLM-curated personal knowledge base in your project — Andrej Karpathy's LLM Wiki pattern, designed to scale to thousands of pages without becoming a context bottleneck. Now with an optional compiled graph layer for typed, provenance-backed relationships.