Search memory files for keywords, patterns, or categories. Returns structured results grouped by file with context.
How this skill is triggered — by the user, by Claude, or both
Slash command
/swannysec-context-keeper:memory-searchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Search across memory files for keywords, patterns, or past decisions. Returns structured results grouped by file with line numbers and category tags.
Search across memory files for keywords, patterns, or past decisions. Returns structured results grouped by file with line numbers and category tags.
Parse the user's invocation to extract the query and any flags:
/memory-search <query>
/memory-search --global <query>
/memory-search --sessions <query>
/memory-search --category <name> <query>
Flags can appear in any order relative to the query.
Run the search script via Bash:
bash "${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || echo .)}/tools/memory-search.sh" <parsed-args>
Pass the query and any flags (--global, --sessions, --category <name>) directly to the script.
Note: The corrections queue (.claude/memory/corrections-queue.md) is included in default project memory search scope.
--category, mention which category was usedIf the script returns "No results found", suggest broadening the search:
--global — include global memory (~/.claude/memory/)--sessions — include session history files (last 30 days)--category — if category filtering was used, try without it/memory-search "token budget"
/memory-search --global "naming convention"
/memory-search --sessions "authentication bug"
/memory-search --category decision "database"
/memory-search --category pattern --global "error handling"
npx claudepluginhub joshuarweaver/cascade-ai-ml-agents-misc-1 --plugin swannysec-context-keeperGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.