From error-memory
Interactively gathers error details, cause, solution, rationale, code changes, and tags from context, then logs them to the error memory database via bash script.
How this command is triggered — by the user, by Claude, or both
Slash command
/error-memory:logThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Error Memory Log Log a new error and its solution to build up the error memory database. ## Usage This command is interactive - Claude will gather the required information from the current context and ask for any missing details. ## Process 1. **Gather Error Information** - Extract from the current conversation context: - The error message (required) - What was happening when the error occurred - The source of the error (bash, playwright, read, user, build, api, other) 2. **Document the Analysis**: - What caused the error (required) - How it was solved (required) ...
Log a new error and its solution to build up the error memory database.
/error-memory:log
This command is interactive - Claude will gather the required information from the current context and ask for any missing details.
Gather Error Information - Extract from the current conversation context:
Document the Analysis:
Capture Code Changes (if applicable):
Add Metadata:
Log the Error:
bash $CLAUDE_PLUGIN_ROOT/scripts/log-error.sh --json '{
"errorMessage": "<error message>",
"project": "<project name>",
"projectPath": "<path>",
"source": "<source>",
"whatHappened": "<context>",
"cause": "<why it happened>",
"solution": "<how it was fixed>",
"rationale": "<why the solution works>",
"fileChanged": "<file path>",
"codeBefore": "<code before>",
"codeAfter": "<code after>",
"tags": ["tag1", "tag2"]
}'
Use consistent, meaningful tags:
After solving a database connection error:
bash $CLAUDE_PLUGIN_ROOT/scripts/log-error.sh --json '{
"errorMessage": "SQLSTATE[HY000] [2002] Connection refused",
"project": "my-laravel-app",
"projectPath": "/home/user/projects/my-laravel-app",
"source": "bash",
"whatHappened": "Running php artisan migrate",
"cause": "Database container was not running",
"solution": "Start the database container with docker-compose up -d db",
"rationale": "Laravel needs an active database connection to run migrations",
"tags": ["laravel", "database", "docker", "connection"]
}'
npx claudepluginhub mwguerra/claude-code-plugins --plugin error-memory/fix-errorAnalyzes error logs or stack traces, identifies root cause, predicts resolution time, and suggests proven fixes. Supports --deep, --quick, --preventive modes.
/fix-errorAnalyzes error messages/logs to identify root causes, predict resolution times, and propose proven fixes. Supports --deep, --preventive, and --quick options.
/fix-errorAnalyzes error output to identify root causes, predict resolution times, and propose proven fixes. Supports --deep, --preventive, --quick modes.
/learnRecords lessons learned from input, errors, sessions, or git history into CLAUDE.md. Supports listing, editing, removing entries and git-based automation suggestions.
/debugFast error debugging by tracing backwards from symptoms to root cause. Accepts an error message, bug description, or screenshot and works through observe, trace, and isolate phases.
/debugExecutes structured debugging workflow: checks project memories for prior bugs, applies evidence checklist (errors, traces, DOM, CSS, network, console), tests hypotheses, validates fixes, auto-writes memory.