llm-session-retrospective

Extracts reusable patterns and candidate skills from recent agent session work.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/gmackie/agent-skills --skill llm-session-retrospective-gmackie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: llm-session-retrospective
Source: https://github.com/gmackie/agent-skills/tree/main/skills/llm-session-retrospective
Command: npx skills add https://github.com/gmackie/agent-skills --skill llm-session-retrospective-gmackie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, findutils, ripgrep, and includes scripts (resource) and references (resource) components.

What problem does it solve? Valuable lessons from Codex and Claude Code sessions usually evaporate after the work is done. This Skill reviews recent agent activity across repos and local session directories, then converts it into retrospective reports and concrete skill candidates instead of letting patterns go undocumented. ## Core Features & Use Cases - Automatic context discovery: Searches the current repo, sibling repos, and ~/.claude and ~/.codex directories for plans, design notes, reviews, and TODO files before asking the user for context. - Three operating modes: Produces a retrospective report, a report plus ranked skill candidates, or full starter skill stubs depending on the request. - Classification of findings: Sorts each pattern into keep-local, private skill, public skill, or not-a-skill so project-specific conventions are not promoted incorrectly. - Use Case: After a week of agent-assisted work, ask for a review and receive a dated retrospective in docs/retrospectives/ with a ranked list of skills worth creating. ## Quick Start Review our recent Codex and Claude Code work and tell me what skills we should create.

Frequently Asked Questions about llm-session-retrospective

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

FAQPage Schema
How do I turn recent AI agent sessions into reusable skills?▼

Ask for a retrospective of recent Codex or Claude Code work. The Skill searches the current repo, sibling repos, and local agent directories, then produces a report with a ranked list of candidate skills and optional starter stubs.

How to review Claude Code and Codex session history for patterns?▼

The Skill automatically scans docs, plans, design notes, reviews, and TODO files in the repo plus ~/.claude and ~/.codex. It classifies repeated decisions and failures into reusable patterns rather than writing a chronological summary.

Does the retrospective write files into my repository?▼

Yes, by default it writes a dated markdown report to docs/retrospectives/ in the current repo, creating the directory if needed. It only writes into a shared agent-skills repo when you explicitly request cross-project harvesting.

What is the difference between report, propose, and scaffold modes?▼

Report mode produces only the retrospective, propose mode adds ranked skill candidates, and scaffold mode additionally generates starter skill stubs. The mode is inferred from your request and defaults to propose when unclear.

When should a pattern not become a public skill?▼

Keep a pattern private or local when it references internal services, exposes sensitive product or customer context, or is tightly coupled to one team or monorepo. Public skills should solve repeatable problems across multiple repos or sessions.