amia-session-memory

Store and retrieve PR review state, integration handoffs, and release history across Claude Code sessions.

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/Emasoft/ai-maestro-integrator-agent --skill amia-session-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amia-session-memory
Source: https://github.com/Emasoft/ai-maestro-integrator-agent/tree/main/skills/amia-session-memory
Command: npx skills add https://github.com/Emasoft/ai-maestro-integrator-agent --skill amia-session-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Claude Code sessions have limited context; ongoing PR reviews, handoffs, and release decisions can be lost between sessions. This skill ensures continuity by persisting and retrieving memory across PR reviews, integration tasks, and releases, enabling seamless resumption.

Core Features & Use Cases

  • Save and retrieve PR review state, integration handoffs, and release history to resume work without re-reading everything.
  • Maintain patterns learned, blockers, and decisions across sessions for consistent quality gates and outcomes.
  • Provide on-demand memory loading, freshness checks, and structured memory updates to guide future work.

Quick Start

Instruct AMIA to load the latest memory and resume the PR review from where it left off.

Frequently Asked Questions about amia-session-memory

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

FAQPage Schema
How do I persist PR review state across Claude Code sessions?

You persist PR review state by storing review progress, blockers, and decisions in structured session memory, enabling seamless cross-session resumption without re-reading everything.

What is session memory for AI assistant context persistence?

Session memory for AI assistant context persistence stores PR review state, integration handoffs, and release history to maintain continuity and guide future decisions across separate Claude Code sessions.

Can I restore integration handoff context after a session expires?

Yes, you restore integration handoff context after a session expires by loading on-demand memory that retrieves stored handoff documents and release history to resume work.

Does session memory work with GitHub PR and issue comments?

Yes, session memory works with GitHub PR and issue comments by applying stored context across comment threads to maintain cross-session work continuity and support structured updates.

How do I check memory freshness before resuming a PR review?

You check memory freshness before resuming a PR review by using the built-in freshness verification feature, which validates that stored session context is current enough to guide future decisions.

What are the limitations of storing release history across sessions?

Limitations of storing release history across sessions include reliance on structured memory updates and on-demand loading, meaning context continuity depends on actively saving session state before expiration.