skills.rest
NauelG
NauelGCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Conducts a retrospective on a coding session to propose agent environment improvements.

28|1|Updated Mar 15, 2026
Search Tags:#coding standards#retrospective#agents.md#session logs#coding session#agent improvement#workflow review
One-click install
npx skills add https://github.com/NauelG/astro-blocks --skill retro-nauelg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/NauelG/astro-blocks/tree/main/.agents/skills/retro
Command: npx skills add https://github.com/NauelG/astro-blocks --skill retro-nauelg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a coding session, it is hard to know why the AI agent struggled, made mistakes, or wasted tool calls. This Skill reviews session logs and turns those observations into concrete improvement proposals for the agent's environment. ## Core Features & Use Cases - Session Analysis: Reads primary sources and session logs for a specified session, defaulting to the current one. - Improvement Categories: Evaluates navigation, automated checks, coding standards, AGENTS.md size, tool economy, no-op instructions, and information access. - Prioritized Output: Presents improvement candidates ordered by severity, following the writing-for-agents style guide. - Use Case: After a long debugging session where the agent repeatedly failed to find a config file, run a retrospective to get a recommendation for adding a navigation pointer to AGENTS.md. ## Quick Start Ask the agent to run a retrospective on the current coding session and suggest environment improvements.

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 a coding session?▼

Invoke the retro skill and optionally specify which session to review. If no session is specified, it defaults to the current one, reads the session logs, and presents improvement candidates ordered by severity.

What kinds of improvements does a coding session retrospective suggest?▼

It suggests navigation pointers, new automated checks like linting or tests, coding standards rule changes, AGENTS.md cleanup, tool economy fixes, removal of no-op instructions, and better information access such as teed dev server logs.

Can the retro skill review a past session instead of the current one?▼

Yes. Specify the session you want reviewed and the skill will search through session logs on the machine to find the primary sources for that session before analyzing it.

When should I not use a session retrospective?▼

Avoid it when the issue is a one-off code bug rather than an environment or workflow problem. The skill targets steering files, checks, and tooling, not fixing the code itself.

Does the retrospective modify AGENTS.md or coding standards automatically?▼

No. It presents improvement candidates to the user in order of severity. Changes to AGENTS.md, CODING_STANDARDS.md, or other files are applied only after the user approves them.

Related Skills

Explore More Software Engineering Skills→
AO-HySAO-HyS

retro

Conducts a retrospective on a coding session to suggest agent environment improvements.

Official
Intermediate
mattpocockmattpocock
242.8k

retro

Conducts a retrospective on a coding session to suggest agent environment improvements.

Community
Intermediate
AngelWings1997AngelWings1997

go-code-review

Enforce gofmt, go vet, and golangci-lint checks during Go code reviews.

Community
Intermediate
unacmsunacms
318

neuron-test-engineer

Automate testing of Neuron AI agents, RAG systems, and workflows.

Official
Advanced