Skip to content
Productivity
Skill

/replay-learnings

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".

From plugin
pro-workflow
2.9k41 skills8 agents23 commands24 hooks
Install
$ npx -y skills add rohitg00/pro-workflow --skill replay-learnings --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/replay-learnings

Context preview

The summary Claude sees to decide when to auto-load this skill.

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".

SKILL.md

replay-learnings.SKILL.md
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:

   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.
Read more
Ships withpro-workflow

Claude Code learns from your corrections: self-correcting memory that compounds over 50+ sessions. Context engineering, parallel worktrees, agent teams, and 17 battle-tested skills.

Get the whole plugin

Other skills on pro-workflow.