pmm-update

Detect and apply upstream Poor Man's Memory migrations in Claude Code projects.

15|8|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/NominexHQ/pmm-plugin --skill pmm-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pmm-update
Source: https://github.com/NominexHQ/pmm-plugin/tree/main/local/pmm-update
Command: npx skills add https://github.com/NominexHQ/pmm-plugin --skill pmm-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Poor Man's Memory installations can drift away from upstream system templates, hooks, and skill files after marketplace updates, leaving migrations, permissions, and configs outdated unless someone tracks and applies each change manually.

Core Features & Use Cases

  • Version awareness: Reads local pmm/version.json and compares it against a fresh clone of the upstream repo to determine whether the installed skill set matches.
  • Structured reporting: Produces an UPDATE_AVAILABLE report that highlights modified, added, deleted, and merge-worthy files, giving the user a clear picture of what would change before approval.
  • Safe execution: Applies only approved changes by overwriting system files, deleting removed artifacts, merging settings additively, reinstalling updated hooks, and committing the results without touching memory/ or user data.

Quick Start

Ask Claude to run /pmm-update to compare your PMM system to upstream and apply approved updates safely.

Frequently Asked Questions about pmm-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update Poor Man's Memory system files to match upstream?

Run /pmm-update to compare your local version.json against a shallow clone of the upstream repo, generate a tactical report of file changes, and apply approved migrations to sync your PMM installation.

What happens to my memory and user data when applying upstream migrations?

Upstream migrations never touch memory/ or user data; the update process only overwrites system files, deletes removed artifacts, and additively merges settings to preserve your stored information.

How does version detection work for Claude Code plugin updates?

The system reads local pmm/version.json metadata and compares it against a fresh shallow clone of the upstream repository to determine whether your installed skills, hooks, and templates match expected versions.

Can I review file changes before a git migration overwrites my project?

Yes, the skill generates an UPDATE_AVAILABLE report highlighting modified, added, deleted, and merge-worthy files, asking for your approval before overwriting system files or deleting artifacts.

Do I need git installed to sync Claude Code plugin templates with upstream?

Git is required because the update process creates a temporary shallow clone of the upstream repo to compare local metadata and prepare file diffs for the migration report.

Why are my Claude Code hooks and skill files outdated after a marketplace update?

PMM installations drift from upstream system templates, hooks, and skills after marketplace updates unless migrations are tracked and applied manually, which this tool automates by detecting and syncing version differences.