retro

Invoke the retro skill and optionally specify which session to review; it defaults to the current session. It reads the session logs, identifies improvement candidates across categories like navigation and automated checks, and presents them ordered by severity.

It suggests navigation pointers for hard-to-find files, automated checks like linting or tests to catch mistakes, new or clarified coding standards for the reviewer agent, trimming of oversized AGENTS.md files, and fixes for token-inefficient tool calls.

The review agent should enforce coding standards. The implementation agent has the most context pressure from exploration, coding, and debugging, while the review agent receives only a diff and has spare capacity for standards enforcement.

AGENTS.md is pushed into every agent's context, so it should be used sparingly, mostly for navigation pointers. CODING_STANDARDS.md is read only during review, making it the right place for enforcement rules, with doc pointers if it exceeds 1,000 lines.

No-ops are instructions in steering files that do not actually change the agent's behavior. The retrospective flags them so large, unwieldy steering files can be trimmed to only effective guidance.