skills.rest
Suge8
Suge8COMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Reviews coding session transcripts to propose agent environment improvements.

Updated Sep 14, 2026
Search Tags:#workflow#retrospective#process improvement#coding agent#session review#agent environment#jsonl transcript
One-click install
npx skills add https://github.com/Suge8/skills --skill retro-suge8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Suge8/skills/tree/main/workflow/retro
Command: npx skills add https://github.com/Suge8/skills --skill retro-suge8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a coding session, it is hard to know whether friction came from the task itself or from a misconfigured agent environment. This Skill systematically reviews a session's raw transcript to find improvement candidates for guidance files, automated checks, tooling, and information access. ## Core Features & Use Cases - Session Transcript Analysis: Reads the full JSONL session record, examining every tool call and its result rather than relying on conversation summaries. - Five-Category Audit: Checks navigation friction, missing automated checks, guidance bloat in AGENTS.md and skills, tool-call economics, and information access gaps, each backed by session evidence. - Prioritized Recommendations: Presents candidates ranked by severity with suggested changes and costs, waiting for user selection before editing anything. - Use Case: After an agent spent many rounds hunting for a file, run a retrospective to identify the missing AGENTS.md context pointer and propose the exact documentation fix. ## Quick Start Ask the agent to run a retrospective on the current coding session and propose improvements to the agent environment.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I run a retrospective on an AI coding session?▼

Invoke the retro skill after a session; it reads the raw JSONL transcript stored under the agent's session directory and audits every tool call. It then presents evidence-backed improvement candidates ranked by severity for you to approve.

What does a coding session retrospective actually improve?▼

It improves the agent environment rather than judging session outcomes. Candidates target AGENTS.md navigation pointers, automated lint or test checks, outdated guidance, expensive tool calls, and missing information channels like dev server logs.

Where are agent session transcripts stored for review?▼

Sessions are stored as JSONL files under ~/.pi/agent/sessions/<encoded-directory-path>/, organized by working directory. If the user does not specify one, the current session is used by default.

Does the retro skill edit files automatically?▼

No. It only presents ranked candidates with suggested changes and their costs, then waits for the user to pick which ones to apply. Documentation edits follow the writing-for-agents skill's conventions.

When should I not use a session retrospective?▼

Skip it when the goal is evaluating the quality of a single session's output rather than improving the environment. It is designed for recurring friction patterns in guidance, checks, tooling, and information access, not one-off result reviews.

Related Skills

Explore More Software Engineering Skills→
Largo2z9Largo2z9
1

export-session

Export Claude Code sessions into structured markdown transcripts for archiving.

Community
Intermediate
pattobrienpattobrien
2

writing-for-agents

Write skills, AGENTS.md, and CLAUDE.md documents that agents follow predictably.

Community
Intermediate
quanngynxquanngynx

Writing Hookify Rules

Write Hookify rules with YAML frontmatter and regex conditions for agent events.

Community
Intermediate
caovinhphuccaovinhphuc

verification-loop

Automates end-to-end verification of Claude Code sessions before merge.

Community
Advanced