pmm-save

Persist Claude Code session state changes into git-backed memory files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude Code sessions can lose meaningful decisions, lessons, and milestones unless every interaction is synthesized and stored; pmm-save ensures each active session state is summarized, merged into the appropriate files, and committed to git so memory compounds instead of rots.

Core Features & Use Cases

  • Config-aware orchestration: Reads memory/config.md to respect maintain agent model, strategy, verbosity, active files, visibility, decay rules, and commit preferences before touching any files.
  • Intelligent skipping and hydration: Detects empty work sessions to avoid unnecessary writes, hydrates template-only files when other files are populated, and synthesizes the session delta to guide downstream agents.
  • Agent-driven maintenance: Dispatches single or tiered maintain agents with precise prompts, enforces file rules (append-only, attribution tags, decay scoring for Tier 2), and finally commits with an optional auto-push while reporting per verbosity settings.
  • Background-safe execution: Supports sequential background saves that monitor for running tasks, handles maintain agents and git commands autonomously, and respects visibility guards like PII handling and protected files.

Quick Start

Use pmm-save to synthesize what changed and commit it before closing the session.

Frequently Asked Questions about pmm-save

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

FAQPage Schema
How do I save Claude Code session memory between tasks?

To save Claude Code session memory, you need a structured approach that synthesizes decisions and milestones into persistent files. This ensures session state changes are merged and committed to git so memory compounds instead of being lost when the session closes.

What is config-driven agent dispatch for session state maintenance?

Config-driven agent dispatch is a mechanism that reads configuration files to respect agent models, strategies, and decay rules before modifying session memory. It automatically orchestrates maintenance tasks by dispatching agents with precise prompts to handle memory updates.

How do I auto-commit structured session memory changes to git?

You can auto-commit structured session memory changes by applying configuration rules that synthesize the session delta and commit the updated files to git. This process optionally pushes changes automatically while reporting results based on your verbosity settings.

Can I use Claude Code sessions without losing decisions and lessons learned?

Yes, Claude Code sessions can retain decisions and lessons by persisting active state changes into git-backed memory files. This prevents meaningful milestones from rotting by ensuring every interaction is synthesized, merged, and committed before closing.

Does session memory maintenance handle empty work sessions and template files?

Intelligent skipping and hydration detect empty work sessions to avoid unnecessary git writes. When other files are populated, the system hydrates template-only files to ensure the session delta is properly synthesized for guiding downstream agents.

What are the limitations of background-safe session saves for agent workflows?

Background-safe session saves require monitoring for running tasks and handle git commands autonomously. While they support sequential execution and visibility guards like PII handling, they depend on strict config rules to enforce append-only updates and decay scoring for Tier 2 files.