retro

作者: mattpocock

对一次编码会话进行回顾。

npx skills add https://github.com/mattpocock/skills --skill retro

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? Read the repo's own check command first (its package.json/build-tool lint/check scripts, its CI workflow), so a check that already exists but sits unwired or silently broken is the finding, not a reinvention. A repo with no guardrail (no pre-commit hook and no CI job running its lint/typecheck/test command) is itself a finding: an un-linted repo is a standing missed opportunity, not a neutral default. Use when the agent made a mistake an automated check could have caught, or the repo has no guardrail at all.
  • Coding standards: should the reviewer agent be given a new rule to enforce? Should an existing rule be removed or clarified? Classify the violation first: a mechanical one (a fixed syntactic pattern, a banned API, an import shape, a file-location rule) gets a deterministic check, full stop: a custom rule in the repo's own linter, a new pre-commit hook, or a new CI job, whichever the repo's language and existing guardrail make cheapest. Default to building the check over writing the rule. Reserve CODING_STANDARDS.md for genuine judgement calls (cross-file consistency, "matches the surrounding style," anything no guardrail could ever substitute for). 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.
  1. 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.

来自 mattpocock 的更多技能

ask-matt
mattpocock
询问哪种技能
communicationresearchproductivity
chief-of-staff
mattpocock
通过协调子代理,在单次会话中推进长期目标。
productivityproject-managementcommunication
claude-handoff
mattpocock
将当前对话移交给一个全新的后台代理,该代理会立即接手工作。
codebase-design
mattpocock
用于设计深度模块的共享词汇。当用户想要设计或改进模块接口、寻找深化机会、决定接缝位置、使代码更易测试或便于AI导航,或当其他技能需要深度模块词汇时使用。
designdevelopmentcode-review
code-review
mattpocock
审查自某个固定点(提交、分支、标签或合并基准)以来的变更,从两个维度进行——标准(代码是否遵循该仓库记录的编码标准?)和规范(代码是否符合原始问题/产品需求文档的要求?)。通过并行子代理运行两项审查,并并排报告结果。当用户希望审查某个分支、拉取请求、进行中的变更,或要求“从X开始审查”时使用。
testingdevelopmentcode-review
design-an-interface
mattpocock
使用并行子代理为一个模块生成多个截然不同的界面设计。当用户想要设计API、探索界面选项、比较模块形态或提到“设计两次”时使用。
developmentdesignapi
diagnosing-bugs
mattpocock
诊断循环,用于处理顽固错误和性能回归。当用户说“诊断/调试这个”,或报告某些东西损坏、抛出异常、失败或缓慢时使用。
testingdevelopmentcode-review
domain-modeling
mattpocock
构建并完善项目的领域模型。当用户希望确定领域术语或通用语言、记录架构决策,或其他技能需要维护领域模型时使用。
designdevelopmentdocument