session-retrospective

Yes, you can route repeated workflows and patterns directly to new or modified skill proposals. The retrospective process identifies recurring processes during the session and generates actionable creation or modification proposals instead of just documenting them in CLAUDE.md.

Routing logic for learnings directs project-specific details to the project CLAUDE.md, universal patterns to the global ~/.claude/CLAUDE.md, and repeated workflows to skill creation or modification proposals, ensuring each learning reaches the appropriate document management target.

You analyze git activity by inspecting session history alongside existing CLAUDE.md and skill data to identify actionable process improvements. This inspection extracts learnings from recent repository changes and generates concise proposals for document updates.

No specific dependencies are required to run a session-retrospective. It operates by directly inspecting the current session context, git activity, and existing CLAUDE.md files within your workspace to automatically produce actionable routing proposals.

You should avoid using a session retrospective when your session lacks meaningful conversation history or git activity to analyze, as the process relies on extracting concrete learnings and routing logic from actual workspace context to generate actionable proposals.