reflect

Spawns three parallel review subagents over a session transcript to route learnings into skill edits.

3|2|Updated Aug 28, 2026
One-click install
npx skills add https://github.com/adjohn/pstack --skill reflect-adjohn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/adjohn/pstack/tree/main/skills/reflect
Command: npx skills add https://github.com/adjohn/pstack --skill reflect-adjohn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Valuable lessons from a working session—corrections, tool quirks, missed triggers—are usually lost when the conversation ends. This Skill mines the active Claude Code transcript for durable learnings and turns them into concrete, approved edits to existing skills. ## Core Features & Use Cases - Parallel multi-lens review: Launches three reviewer subagents (judgment, tooling, divergent) over the session transcript, each with a dedicated prompt template and model tier. - Structured synthesis: A synthesizer subagent merges findings into an Accepted / Rejected / Backlog list with durability, specificity, and convergence criteria. - Approval-gated application: Edits are applied only after explicit user approval, routed to existing skill sections, description tuning, or new skill creation via skill-creator. - Use Case: After a long debugging session where the agent discovered a non-obvious test command and the user corrected its approach twice, say "reflect" to capture those lessons as permanent improvements to the relevant skills. ## Quick Start Say "reflect" after a complex task completes to review the session and apply approved learnings to your skills.

Frequently Asked Questions about reflect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture learnings from a Claude Code session?▼

Invoke the reflect skill after a complex task completes. It locates the active session transcript, spawns three parallel reviewer subagents, synthesizes their findings, and presents approved edits to your existing skills for confirmation.

What do the three reviewer subagents in reflect do?▼

Each reviewer applies a different lens: judgment surfaces durable principles from mistakes and corrections, tooling captures concrete commands and technical facts, and divergent finds blind spots and second-order effects the others miss.

Does reflect modify my skills automatically?▼

No. The synthesizer produces an Accepted, Rejected, and Backlog list, and the parent agent waits for explicit user approval before applying any edit. Backlog items are filed to your team's tracker separately.

Where does reflect find the session transcript?▼

It derives the transcript directory from the current working directory under ~/.claude/projects/<slug>/, then matches the JSONL file whose first user message contains the conversation's opening prompt. It never globs across other project directories.

When should I not use reflect on a conversation?▼

Skip it when the session was trivial, off-topic, or already covered by an existing skill the agent followed correctly. One-off events and implementation details that drift, like SHAs or version numbers, are not durable learnings.