Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By killerapp
Memory-augmented development workflows for Claude Code. Provides commands for planning, implementation, debugging, and research with persistent memory.
npx claudepluginhub killerapp/mem8-plugin --plugin mem8Debug issues during manual testing by investigating logs, database state, and git history
Create git commits for changes made during this session
Generate a comprehensive PR description following the repository's standard template
Implement an approved technical plan from memory/plans/
Set up a local review environment for a colleague's branch with worktree
CLI tool discovery, documentation, and recommendation agent. Use when (1) setting up a new project and want CLI recommendations, (2) documenting a CLI tool or recipe discovered during development, (3) analyzing codebase for CLI tool opportunities, or (4) looking for CLI patterns to solve a specific task.
Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :)
Locates files, directories, and components relevant to a feature or task. Call `codebase-locator` with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.
codebase-pattern-finder is a useful subagent_type for finding similar implementations, usage examples, or existing patterns that can be modeled after. It will give you concrete code examples based on what you're looking for! It's sorta like codebase-locator, but it will not only tell you the location of files, it will also give you code details!
The research equivalent of codebase-analyzer. Use this subagent_type when wanting to deep dive on a research topic. Not commonly needed otherwise.
Expert guidance for working with Obsidian vaults including Obsidian Flavored Markdown (OFM) syntax, organization best practices, daily/weekly task workflows, vault maintenance, and automation. This skill should be used when working with Obsidian notes, organizing vault structure, setting up task management workflows, or integrating with Obsidian tooling.
CLI power tools for AI-assisted development. Use when (1) needing recommendations for CLI tools to install, (2) processing JSON/YAML data with jq/yq, (3) searching code with ripgrep or ast-grep, (4) documenting a CLI tool or multi-tool recipe you've discovered, (5) wanting to learn CLI patterns for data pipelines, or (6) setting up a new project and want CLI recommendations. Supports three modes - init (project scan), document (capture new recipes), and recommend (codebase analysis).
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Persistent memory system for AI coding sessions — cross-tool memory sharing with 6-dimensional hybrid search
PowerMem intelligent memory for Claude Code: add, search, update, and delete memories with Ebbinghaus decay and multi-agent support.
Persistent memory across Claude Code sessions using Cognis
Persistent memory for AI coding agents. Survives across sessions and compactions.
Universal memory runtime — cross-session cognitive memory for Claude Code. Remembers decisions, patterns, and context across coding sessions.
Curated persistent memory for Claude Code. Write gate prevents bloat — only behavior-changing facts get saved. Tiered architecture: daily logs, structured registers, and auto-loaded working memory.
Official Claude Code plugin for mem8 - memory-augmented development workflows.
mem8 enhances Claude Code with persistent memory and structured workflows:
memory/ directory.claude/settings.jsonFor full functionality including search, sync, and diagnostics:
# Install with uv (fast, modern Python package manager)
uv tool install mem8
:::tip Don't have uv? Install it first:
curl -LsSf https://astral.sh/uv/install.sh | sh
:::
Verify CLI installation:
mem8 --version
mem8 status
Add mem8 marketplace and install the plugin:
/plugin marketplace add killerapp/mem8-plugin
/plugin install mem8@mem8-official
The memory/ directory will be created automatically.
For automatic installation across your team, add to .claude/settings.json:
{
"extraKnownMarketplaces": {
"mem8": {
"source": {
"source": "github",
"repo": "killerapp/mem8-plugin"
}
}
},
"enabledPlugins": ["mem8@mem8-official"]
}
When team members trust the repository, mem8 installs automatically.
commands/
├── commit.md # Create well-structured commits
├── debug.md # Debug issues with memory context
├── describe-pr.md # Generate PR descriptions
├── implement.md # Implement from plans
├── local-review.md # Set up review environments
├── plan.md # Create implementation plans
├── research.md # Research codebase
└── validate.md # Validate implementations
agents/
├── codebase-analyzer.md # Deep code analysis
├── codebase-locator.md # Find relevant files
├── codebase-pattern-finder.md # Discover patterns
├── memory-analyzer.md # Deep memory analysis
├── memory-locator.md # Find relevant memory
└── web-search-researcher.md # Web research
skills/
├── obsidian-skill/ # Obsidian vault management
│ ├── SKILL.md # OFM syntax and best practices
│ ├── references/ # Comprehensive guides
│ ├── scripts/ # Vault health utilities
│ └── assets/templates/ # Note templates
└── para-pkm/ # PARA knowledge management
├── SKILL.md # PARA method implementation
├── references/ # Decision guides and patterns
├── scripts/ # Automation (init, validate, archive)
└── assets/ # Templates for projects/areas
Created automatically during plugin installation:
memory/
├── plans/ # Implementation plans and technical designs
├── research/ # Research documents and findings
├── prs/ # Pull request descriptions and reviews
└── docs/ # Documentation and notes
# Research your codebase
/mem8:research
# Create an implementation plan
/mem8:plan
# Implement the plan
/mem8:implement memory/plans/your-plan.md
# Validate implementation
/mem8:validate memory/plans/your-plan.md
# View plugin status and available commands
mem8 status
# Detailed view with paths
mem8 status --detailed
The plugin is defined by:
.claude-plugin/plugin.json - Plugin metadata and configuration.claude-plugin/marketplace.json - Marketplace catalog definitionhooks/hooks.json - Post-install automation hooksscripts/ - Cross-platform setup scriptsThe plugin automatically runs:
memory/ directory structure.claude/.mem8-plugin marker for detectionScripts support Linux/macOS (bash), Windows (batch), and PowerShell.
.claude-plugin/plugin.json version/plugin marketplace add YOUR_ORG/mem8-plugin
/plugin install mem8@your-marketplace
git clone https://github.com/killerapp/mem8-plugin.git
cd mem8-plugin
# Test changes locally
/plugin install file://$(pwd)@mem8-official