agent-teams
Coordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team…
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".
$ npx -y skills add rohitg00/pro-workflow --skill replay-learnings --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/replay-learningsContext 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".
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".
Like muscle memory for your coding sessions. Find and surface relevant learnings before you start working.
Use when starting a new task, saying "what do I know about", "before I start", "replay", or "remind me about".
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.
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)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.
Repo: rohitg00/pro-workflow
Coordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team…
Auto-configure quality gates, hooks, and settings for a new project. Detects project type and sets up appropriate tooling. Use when onboarding a new codebase.
Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change…
Capture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never…
Smart context compaction with state preservation. Saves critical files, task progress, and working state before compaction, restores after. Use before manual…
Master the four operations of context engineering — Write, Select, Compress, Isolate. Manage token budgets, compaction strategies, and context partitioning to…