claude-mem
claudecodexPersistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
Workflow and knowledge layer for teams coding with Claude Code — small repo-scoped context at session start, facts filed where they have a reader (issues, PRs, ADRs, team wiki, logbook), the rest pulled on demand over MCP. Ships the build skills too: orient, grilling, to-epic, build, tdd, debug, document, experiment, handover, file-issue, triage.
Plugin lore from marketplace lore in buchbend/lore. Commands read from the repo's manifest — 2 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use and it starts local MCP servers. The exact commands are listed below; read them before installing.
lore:contextShow the full timeline of context Lore injected this session.
lore:debugSystematic root-cause debugging with a hard circuit breaker. Use when a bug resists fixing, a test keeps failing, a teammate is stuck after repeated fix attempts, or you catch yourself guessing at fixes instead of finding the cause.
lore:documentBring a repo's Diátaxis docs (tutorial, how-to, reference, explanation) in line
lore:experimentRun one experiment and record it as one lab entry — write the question and the expected result before the run, run it, then write the entry with `lore lab add` and commit its file on the current branch. Use when the user wants to try, measure, calibrate, benchmark or test a hypothesis, says "run an
lore:file-issueWrites issue text and files it — resolve the team's writing
lore:grillingInterview the user relentlessly about a plan or design, and sharpen the domain model as decisions land (CONTEXT.md terms, ADRs). Use when the user wants to stress-test a plan before building, says "grill me" or "grill with docs", uses any other 'grill' trigger phrase, or wants to pin down domain ter
lore:handoverHand work over to a later session, in two parts. Part one writes a handover note so the next session continues this one after /clear or compaction; SessionStart points the next session to the note automatically. Part two writes the handover section for work that stops before its finish point, turns
lore:inboxProcess files from wiki inboxes and the root inbox.
lore:mapKeep the system map true. The map phase scans the local checkouts
lore:orientThe first step of a piece of work — the session does its own homework, then
lore:systemBring every local checkout of a system to its target branch, using
lore:tddTest-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
lore:to-epicTurn the current conversation or a plan/PRD into a PRD file under docs/prd/ plus
lore:triageReview every open issue and open PR of one repo against the code at HEAD. Find what
loreruns: lore mcp
lore hook session-start
lore hook capture --event session-start
lore hook pre-compact
lore hook capture --event pre-compact
lore hook user-prompt-submit
lore hook capture --event session-end
lore hook token-usage
lore hook stop
lore hook spawn-model-gate
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
1 MCP server
AI memory system — mine projects and conversations into a searchable palace. 47 MCP tools, auto-save hooks, guided setup.
3 skills · 6 commands · 1 MCP server · hooks
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
8 skills · 1 MCP server
Claude Skills for Obsidian
6 skills
Code intelligence powered by a knowledge graph. Provides execution flow tracing, blast radius analysis, and augmented search across your codebase.
12 skills · 1 MCP server · hooks
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.