跳到正文
cccskills
免费在 GitHub 公开

review-plan

Review an implementation plan before coding across architecture, code quality, tests, and performance. Compare concrete options for each issue, explain effort and risks, and choose a direction through an interactive review.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Structured plan review across 4 axes before writing any code (inspired by Garry Tan's workflow)

查看安装方法

适用场景

  • Review a specification before implementation
  • Check component boundaries and dependencies
  • Find missing tests and failure scenarios
  • Compare fixes by effort, risk, and maintenance

包含的文件(1)

  • SKILL.md3.5 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Review plan before implementation

Review the current plan thoroughly before making any code changes. For every issue or recommendation, explain the concrete tradeoffs, give an opinionated recommendation, and ask for user input before assuming a direction.

Engineering preferences

Use these to guide your recommendations (override with project-specific CLAUDE.md preferences if they exist):

  • DRY is important: flag repetition aggressively
  • Well-tested code is non-negotiable: prefer too many tests over too few
  • Code should be "engineered enough": not under-engineered (fragile, hacky) and not over-engineered (premature abstraction, unnecessary complexity)
  • Err on the side of handling more edge cases, not fewer
  • Bias toward explicit over clever; thoughtfulness over speed

Review pipeline

Work through each section sequentially. After each section, pause and ask for feedback before moving on.

1. Architecture review

Evaluate:

  • Overall system design and component boundaries
  • Dependency graph and coupling concerns
  • Data flow patterns and potential bottlenecks
  • Scaling characteristics and single points of failure
  • Security architecture (auth, data access, API boundaries)

2. Code quality review

Evaluate:

  • Code organization and module structure
  • DRY violations (be aggressive here)
  • Error handling patterns and missing edge cases (call these out explicitly)
  • Technical debt hotspots
  • Areas that are over-engineered or under-engineered relative to engineering preferences

3. Test review

Evaluate:

  • Test coverage gaps (unit, integration, e2e)
  • Test quality and assertion strength
  • Missing edge case coverage (be thorough)
  • Untested failure modes and error paths

4. Performance review

Evaluate:

  • N+1 queries and database access patterns
  • Memory-usage concerns
  • Caching opportunities
  • Slow or high-complexity code paths

Issue reporting format

For every specific issue found (bug, smell, design concern, or risk):

  1. Describe the problem concretely, with file and line references
  2. Present 2-3 options, including "do nothing" where that's reasonable
  3. For each option, specify: implementation effort, risk, impact on other code, and maintenance burden
  4. Give your recommended option and why, mapped to engineering preferences above
  5. Ask explicitly whether the user agrees or wants to choose a different direction before proceeding

Workflow

  • Do not assume priorities on timeline or scale
  • After each section, pause and ask for feedback before moving on
  • Use AskUserQuestion for structured option selection

Before starting

Ask if the user wants one of two options:

  1. BIG CHANGE: Work through this interactively, one section at a time (Architecture → Code Quality → Tests → Performance) with at most 4 top issues in each section
  2. SMALL CHANGE: Work through interactively ONE question per review section

Tips

  • Combine with .claude/rules/ files for project-specific review criteria
  • Engineering preferences above can be overridden by your project's CLAUDE.md
  • For deeper analysis, use this command with Opus model

Sources

$ARGUMENTS

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Evaluate Claude Code agents, skills, and commands with weighted quality criteria. Get scores, readiness grades, template comparisons, and practical improvement suggestions in Markdown or JSON reports to guide reviews before release.

中文简介正在准备中。当前显示英语简介。

  • Review skills before release
  • Compare agent definitions with reference templates
  • Quickly check critical quality criteria
FlorianBruniaux/claude-code-ultimate-guide62172026年10月20日 更新

Assess a codebase across seven areas, including exposed credentials, security, dependencies, structure, and tests. Receive category scores, findings tied to file locations, and a prioritized improvement plan with smaller tasks that can be completed quickly.

中文简介正在准备中。当前显示英语简介。

  • Assessing the overall health of an inherited project
  • Reviewing exposed credentials and security risks
  • Identifying dependency and test coverage gaps
FlorianBruniaux/claude-code-ultimate-guide62172026年10月20日 更新

Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.

中文简介正在准备中。当前显示英语简介。

  • Finding code patterns to prioritize for cleanup
  • Preparing measurement files for an improvement loop
  • Repeating targeted edits to reduce casts to any
FlorianBruniaux/claude-code-ultimate-guide62172026年10月20日 更新

best-of-n

免费

Generate several separate solutions, compare them against criteria fixed in advance, and verify the selected result through executable checks or an independent reviewer. Keep a proof log documenting candidates, evidence, failures, and remaining limits.

中文简介正在准备中。当前显示英语简介。

  • Comparing implementation options before choosing one
  • Verifying a solution when a wrong choice would be costly
  • Keeping evaluation evidence for delivery or audit
FlorianBruniaux/claude-code-ultimate-guide62172026年10月20日 更新

canary

免费

Monitor a live application after deployment and compare it with a saved baseline, a record of its earlier state. Check page responses, loading times, and new errors, flag persistent changes, and produce a per-page health report.

中文简介正在准备中。当前显示英语简介。

  • Recording a healthy baseline before deployment
  • Monitoring production immediately after deployment
  • Checking key pages for slower responses or failures
FlorianBruniaux/claude-code-ultimate-guide62172026年10月20日 更新

catchup

免费

Rebuild project context after clearing a conversation or returning to work. Review recent Git history, uncommitted changes, and TODO markers to get a structured summary of project status and suggested next steps.

中文简介正在准备中。当前显示英语简介。

  • Restoring project context after /clear
  • Reviewing recent changes after a long break
  • Checking unfinished work before choosing the next task
FlorianBruniaux/claude-code-ultimate-guide62172026年10月20日 更新

查看 FlorianBruniaux 的全部技能

报告此技能的问题