Menú
Deploy the MemoryLane Claude Code plugin by verifying only plugin/marketplace files changed, bumping the plugin version, then committing and pushing.
Write step-by-step automation instructions for a workflow, tailored to your tool (Claude, n8n or Zapier). Best run right after discover-patterns or process-analyst.
(new) Find a person's repeated tasks from their screen activity, and what each one is worth automating, with the time and money saved. Outputs the numbers and data a report is built from, not the visual. Use to analyze processes, mine workflows, or see what is automatable and what it saves. Every figure is labelled and grounded, never made up.
(new) Turn a process analysis into a polished, client-ready report, first an HTML deck you review, then a matching PDF. Use to package an analysis into an exec report or PDF. Shows the deck for approval before making the PDF, and never makes up numbers.
Generate a time report grouped by client/project
Discover repeated workflow patterns from screen activity and suggest automations
Summarize what you've been doing in the last 30 minutes.
| name | deploy-plugin |
| description | Deploy the MemoryLane Claude Code plugin by verifying only plugin/marketplace files changed, bumping the plugin version, then committing and pushing. |
Ship a new version of the MemoryLane Claude Code plugin.
Only these paths may have changes when deploying the plugin:
plugins/memorylane/
.claude-plugin/
Any changes outside these paths must be committed or stashed separately before deploying.
Run git status and git diff --name-only to list all modified, staged, and untracked files.
If any changed file falls outside the allowed paths listed above, stop immediately and tell the user:
Some changes are outside the plugin directory. Please commit or stash them before deploying the plugin.
List the offending files so the user can act on them.
Read plugins/memorylane/.claude-plugin/plugin.json and note the current "version" value.
Increment the patch number by default (e.g. 0.6.0 → 0.6.1). If the user specified a version or bump level (major/minor/patch), use that instead.
Update the "version" field in plugins/memorylane/.claude-plugin/plugin.json.
npm run format
Stage only plugin/marketplace files:
git add plugins/memorylane/ .claude-plugin/
git commit -m "plugin: v<new-version>"
git push origin HEAD
Print the new version and the pushed branch name so the user can verify.