# Resume Work From Session Memory

Teams lose time when agents forget prior decisions, project status, and unfinished tasks. This skill organizes local session memory so Claude, Codex, and Claude Code can continue work with clearer context.

## Install

```bash
npx skillstore add chachamaru127/session-memory
```

## Metadata

- - Slug: chachamaru127-session-memory
- - Version: 1.0.0
- - Author: Chachamaru127
- - GitHub username: Chachamaru127
- - License: MIT
- - Repository: https://github.com/Chachamaru127/claude-code-harness/tree/main/skills/session-memory
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: medium
- - Risk factors: filesystem
- - Quality score: 72
- - Public page: https://skillstore.pages.dev/skills/chachamaru127-session-memory
- - Manifest: https://skillstore.pages.dev/api/skills/chachamaru127-session-memory/manifest

## Capabilities

- Defines a .claude/memory/ structure for session logs, decisions, patterns, and context.
- Guides agents to read prior session context before resuming project work.
- Separates shared decision records from local session logs and state files.
- Provides sample formats for Markdown logs and a JSON context file.
- Reminds users not to record sensitive information in memory files.

## Use Cases

- Continue Development After a Break: Review previous work, unfinished tasks, and project status before starting a new coding session.
- Preserve Team Decisions: Record important technical choices and reusable project patterns in shared Markdown files.
- Create Clear Project Handoffs: Summarize recent progress and next steps so another agent or teammate can continue safely.

## Prompt Templates

### Show Previous Session

```
Show me what happened in the previous session and list the unfinished tasks.
```

### Summarize Project Context

```
Use the session memory files to summarize this project, recent decisions, and current phase.
```

### Update Memory After Work

```
Update the session memory with completed tasks, changed files, important decisions, and next steps. Do not include secrets.
```

### Audit Memory Quality

```
Review the session memory for stale entries, duplicate decisions, missing context, and sensitive information. Suggest a cleaner structure.
```

## Limitations

- Does not include executable automation or hook files in this package.
- Depends on the agent and user to keep memory files accurate.
- Can accumulate stale or sensitive information if not maintained.
- Uses local files and does not synchronize memory across machines.

## Best Practices

- Keep shared decision and pattern files concise, indexed, and reviewed.
- Exclude credentials, tokens, customer data, and private notes from memory files.
- Periodically prune old session logs and move durable knowledge into decision records.

## Anti Patterns

- Using session memory as a full transcript archive for every interaction.
- Committing local session logs or context files without reviewing their contents.
- Treating stale memory as authoritative when current repository files disagree.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T20:28:29.413\+00:00
- - Summary: Static command-execution, weak-crypto, reconnaissance, and obfuscation findings were false positives caused by Markdown backticks, plain text, and examples in SKILL.md. The meaningful risk is local persistence: the skill directs agents to read and write memory files that may contain sensitive project history if users record it.

## Stats

- - Views: 258
- - Downloads: 4
- - Favorites: 0
- - Popularity score: 0