retro

작성자: mattpocock

Conduct a retrospective on a coding session.

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
Pursue a long-running goal in a single session by co-ordinating subagents.
productivityproject-managementcommunication
claude-handoff
mattpocock
현재 대화를 즉시 작업을 이어받는 새로운 백그라운드 에이전트에게 넘깁니다.
codebase-design
mattpocock
깊은 모듈 설계를 위한 공유 어휘입니다. 사용자가 모듈의 인터페이스를 설계하거나 개선하고, 심화 기회를 찾고, 분할 지점을 결정하며, 코드를 더 테스트 가능하거나 AI가 탐색하기 쉽게 만들고자 할 때, 또는 다른 스킬이 깊은 모듈 어휘를 필요로 할 때 사용합니다.
designdevelopmentcode-review
code-review
mattpocock
고정된 지점(커밋, 브랜치, 태그, 또는 머지 베이스) 이후의 변경 사항을 두 가지 축(Standards: 코드가 이 저장소의 문서화된 코딩 표준을 따르는가? Spec: 코드가 원래 이슈/PRD에서 요청한 내용과 일치하는가?)을 따라 검토합니다. 두 검토를 병렬 하위 에이전트에서 실행하고 나란히 보고합니다. 사용자가 브랜치, PR, 작업 중인 변경 사항을 검토하거나 "X 이후 검토"를 요청할 때 사용하세요.
testingdevelopmentcode-review
design-an-interface
mattpocock
모듈에 대해 병렬 하위 에이전트를 사용하여 근본적으로 다른 여러 인터페이스 디자인을 생성합니다. 사용자가 API를 디자인하거나, 인터페이스 옵션을 탐색하거나, 모듈 형태를 비교하거나, "두 번 디자인하라"고 언급할 때 사용하세요.
developmentdesignapi
diagnosing-bugs
mattpocock
하드 버그 및 성능 회귀를 위한 진단 루프입니다. 사용자가 "진단해줘"/"디버그해줘"라고 말하거나, 무언가 고장/예외/실패/느림을 보고할 때 사용하세요.
testingdevelopmentcode-review
domain-modeling
mattpocock
프로젝트의 도메인 모델을 구축하고 다듬습니다. 사용자가 도메인 용어나 보편적 언어를 확정하거나, 아키텍처 결정을 기록하거나, 다른 스킬이 도메인 모델을 유지해야 할 때 사용합니다.
designdevelopmentdocument