replay-learnings — Claude Code skill: review past lessons
The replay-learnings skill searches project memory and similar sessions for lessons tied to a new task. Run it before coding to bring earlier corrections into view.
MIT ★ 2,966 updated 2026-09-29
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflowWhat replay-learnings does
The skill pulls keywords from the task, then searches .claude/LEARNED.md, .claude/learning-log.md, and [LEARN] notes in CLAUDE.md. It also checks session history for similar work, ranks matching lessons by relevance, and prepares a briefing with mistake context and suggested next steps.
When it finds no matching lessons, it recommends starting with the scout agent. Sessions with a higher correction rate get flagged for extra care. The search depends on relevant entries in the project’s memory files, so the briefing reflects what those files and session history contain.
What it helps with
- find earlier corrections related to a new task
- recall mistakes from similar sessions
- surface lessons that match the current work
- spot past sessions with high correction rates
Example prompts for the agent
- Before I refactor authentication, find earlier lessons and mistakes to review.
- What have we learned about
middlewarein past tasks? - Check similar session history before I work on the tests.
How to install replay-learnings
1Plugin marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflowThis installs the whole pro-workflow plugin with all its skills
2Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill replay-learnings -a claude-code3Manually: put the files in place
~/.claude/skills/replay-learnings/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/replay-learnings/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill replay-learnings -a codex2Manually: put the files in place
.agents/skills/replay-learnings/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill replay-learnings -a cursor2Manually: put the files in place
.cursor/skills/replay-learnings/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rohitg00/pro-workflow skills/replay-learnings2Manually: put the files in place
.github/skills/replay-learnings/SKILL.md1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill replay-learnings -a gemini-cli2Platform CLI
gemini skills install https://github.com/rohitg00/pro-workflow --path skills/replay-learningsManually: put the files in place
.devin/skills/replay-learnings/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about replay-learnings
How do I install replay-learnings in Claude Code?
Add the marketplace with /plugin marketplace add rohitg00/pro-workflow, then install the plugin with /plugin install pro-workflow@pro-workflow.
What does replay-learnings do?
It searches project memory and similar session history for lessons related to the current task. It ranks matches by relevance and presents them with context and suggested actions.
Which files does replay-learnings search?
It looks for matches in .claude/LEARNED.md, .claude/learning-log.md, and [LEARN] notes in CLAUDE.md.
Source text
SKILL.md · MIT
---
name: replay-learnings
description: Surface past learnings relevant to the current task before starting work. Searches correction history, recalls past mistakes, and applies prior patterns. Use when starting a task, saying "what do I know about", "previous mistakes", "lessons learned", or "remind me about".
---
# Replay Learnings
Like muscle memory for your coding sessions. Find and surface relevant learnings before you start working.
## Trigger
Use when starting a new task, saying "what do I know about", "before I start", "replay", or "remind me about".
## Workflow
1. Extract keywords from the task description (e.g. "auth refactor" → `auth`, `middleware`, `refactor`).
2. Search learnings/memory for matching patterns:
```bash
grep -i "auth\|middleware" .claude/LEARNED.md 2>/dev/null
grep -i "auth\|middleware" .claude/learning-log.md 2>/dev/null
grep -A2 "\[LEARN\]" CLAUDE.md | grep -i "auth\|middleware"
```
3. Check session history for similar work — what was the correction rate?
4. Surface the top learnings ranked by relevance.
5. If no learnings found, suggest starting with the scout agent to explore first.
## Output
```
REPLAY BRIEFING: <task>
=======================
Past learnings (ranked by relevance):
1. [Testing] Always mock external APIs in auth tests (applied 8x)
Mistake: Called live API in tests, caused flaky failures
2. [Navigation] Auth middleware is in src/middleware/ not src/auth/ (applied 5x)
3. [Quality] Add error boundary around auth state changes (applied 3x)
Session history for similar work:
- 2026-02-01: auth refactor — 23 edits, 2 corrections (8.7% rate)
- 2026-01-28: auth middleware — 15 edits, 4 corrections (26.7% rate)
^ Higher correction rate — review patterns before starting
Suggested approach:
- Mock external APIs (learning #1)
- Check src/middleware/ first for auth code (learning #2)
```
## Guardrails
- Rank by relevance, not recency.
- Include the original mistake context so the learning is actionable.
- Flag high correction-rate sessions as areas requiring extra care.
- If no learnings match, say so explicitly rather than forcing irrelevant results.
© Rohit Ghumare · MIT · rohitg00/pro-workflow