emasoft/amia-session-memory

AMIA Session Memory Skill

Overview

Persist and retrieve session context across session boundaries using PR comments, issue comments, and handoff documents.

Prerequisites

• AMIA role understood (quality gates, reviews, merging, releases)
• gh CLI configured and authenticated
• $CLAUDE_PROJECT_DIR set and writable

Instructions

1. Detect triggers — Check for PR numbers, GitHub URLs, or issue refs in user prompt
2. Load memory — PR-related: load PR comment state; integration: load handoff docs from $CLAUDE_PROJECT_DIR/thoughts/shared/handoffs/amia-integration/; release: load release history
3. Verify freshness — Compare timestamps in memory against actual GitHub state (PR status, CI runs, tags)
4. Execute task — Use loaded memory to inform decisions; update memory as work progresses
5. Persist state — Update PR comments with state markers; write handoff docs if work incomplete
6. Verify writes — Confirm PR comments posted and handoff files written

Checklist

Copy this checklist and track your progress:

• [ ] Detect state-based triggers (PR review, integration, release)
• [ ] Load relevant memory (PR comments, handoff docs, release history)
• [ ] Verify memory freshness against GitHub state
• [ ] Execute task using loaded context
• [ ] Persist updated state (PR comments + handoff docs)
• [ ] Verify all writes succeeded

Output

| Memory Type | Storage Location | Format | |-------------|-----------------|--------| | PR Review State | GitHub PR comment | Markdown with HTML state marker | | Integration Patterns | Handoff document | Markdown with timestamped entries | | Release History | Handoff document | Markdown table with release metadata | | CI/CD State | Issue comment or handoff | Markdown with workflow run links |

Output discipline: All scripts support --output-file <path>.

Reference Documents

• memory-architecture — Storage locations and persistence patterns
• memory-retrieval — Triggers and retrieval commands
• memory-updates — Update triggers and commands
• handoff-documents — Handoff format and checklist
• detailed-guide — Error handling, examples, troubleshooting

See references/ directory for remaining documents.

Error Handling

Non-zero exit codes on failure. See detailed guide in Resources.

Resources

• detailed-guide — Full reference
  • Error Handling
  • Examples
  • Memory Architecture
  • What to Remember
  • Memory Retrieval
  • Memory Updates
  • Handoff Documents
  • Integration with Other Skills
  • Troubleshooting
  • Quick Reference Commands
  • State Markers
  • Full Reference Document Listing

Examples

# Resume a PR review from a previous session
gh pr view 42 --json comments --jq '.comments[] | select(.body | contains("AMIA-STATE"))' > /tmp/pr42-state.json
# Load the state marker and continue review from where you left off
# Save updated state when done
gh pr comment 42 --body "<!-- AMIA-STATE: {\"phase\": 3, \"dimensions_completed\": [1,2,3], \"timestamp\": \"2026-03-26T12:00:00Z\"} -->"

Expected result: The session state is loaded from the PR comment containing the AMIA-STATE marker. After completing remaining work, an updated state marker is posted so the next session can resume seamlessly.