---
id: gh-retro
name: "retro"
url: https://skills.yangsir.net/skill/gh-retro
author: mattpocock
domain: ai-dev-tools-workflow
tags: ["retrospective", "coding-session", "agent-improvement", "environment-optimization", "workflow"]
install_count: 268100
rating: 4.90 (120 reviews)
github: https://github.com/mattpocock/skills/tree/main/skills/in-progress/retro
---

# retro

> 此技能用于对一次编码会话进行回顾复盘,通过分析会话日志和代理行为,从导航效率、自动化检查、编码标准、工具经济性、信息访问等维度识别改进点,帮助开发者或团队优化编码代理的工作环境,提升后续运行的效率与质量。

**Stats**: 268,100 installs · 4.9/5 (120 reviews)

## Before / After 对比

### 回顾效率与改进点识别能力对比

**Before**:

在没有这个技能之前,开发者需要手动翻阅大量会话日志,凭经验寻找改进点,容易遗漏关键问题,且耗时较长。

**After**:

此技能自动分析会话过程,按导航、自动化检查、编码标准等维度系统识别改进机会,显著缩短回顾时间,提升改进措施的覆盖率。

| Metric | Before | After | Change |
|---|---|---|---|
| 单次回顾耗时 | 60分钟 | 15分钟 | -75% |
| 识别改进点数 | 2个 | 8个 | +300% |

## Readme

The user has asked for a **retrospective**. You are suggesting improvements to the coding agent's **environment** to improve future runs.

## Steps

1. Call the Skill tool with `writing-for-agents` for the writing style guide.

2. Read the primary sources for the session the user specifies. This may mean searching through session logs on this machine. If the user doesn't specify a session, default to the current one.

3. Look for candidates for improvement in these categories.

- **Navigation**: how easy was it for the agent to find the right files? Are there hidden dependencies between files? Would a **navigation pointer** make it easier? _Use when_ the session took a long time to find a piece of information.
- **Automated checks**: are there automated checks that could catch errors the agent made? Linting, typing, tests, filesystem linters? _Use when_ the agent made a mistake that could have been caught by an automated check.
- **Coding standards**: should the **reviewer agent** be given a new rule to enforce? Should an existing rule be removed or clarified? _Use when_ the reviewer agent failed to catch a mistake.
- **Global AGENTS.md**: are there any steering instructions that should be moved to coding standards (or automated checks) instead? _Use when_ the AGENTS.md file is particularly large - in the repo OR the user's global scope.
- **Tool economy**: did the agent make expensive tool calls that could be streamlined? Is there any custom tooling (CLI's, MCP's) that is particularly token-inefficient? _Use when_ the agent made an expensive tool call.
- **No-ops**: look for instructions in steering files that don't modify the agent's behavior. _Use when_ the steering files are large and unwieldy.
- **Information access**: look for opportunities to increase the agent's access to information. Teeing dev server logs, readonly access to third-party services. _Use when_ a crucial piece of information was not available to the agent.

4. Present these candidates to the user, in order of severity.

## Reference

### Implementation vs Review

Remember that all work goes through two stages: implementation and review. The implementation agent has the most **context pressure**. They are responsible for exploration, writing code, and debugging failures.

The review agent has the least context pressure - it receives a diff, so no exploration needed. It often does not need to write code or debug.

This means that the review agent should be responsible for imposing coding standards, not the implementation agent.

### Files

You have access to several files in the repo:

- `CLAUDE.md`/`AGENTS.md`: these files are pushed to the context window of any agent working in this repo. They should be used incredibly sparingly, usually only for **navigation pointers** to other files.
- `CODING_STANDARDS.md`: this file is read during review, not implementation. Add **navigation pointers** to docs folders if the standards file gets more than 1,000 lines long.
- Docs: use docs as references files, pointed to by other files. Look for existing docs before writing new ones.
- Skills: use skills for docs (since their description goes into the agent's context window), or for user-invoked commands. Follow the advice in the `writing-for-agents` skill.


---
*Source: https://skills.yangsir.net/skill/gh-retro*
*Markdown mirror: https://skills.yangsir.net/api/skill/gh-retro/markdown*