agentsclimarketplace

Code review preferences

Skill bg-szy/TOP-SKILLS/skills/marketplace/code-review-preferences

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install
npx -y skills add bg-szy/TOP-SKILLS --skill code-review-preferences

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when reviewing code, PRs, or discussing code quality standards. Applies team coding standards and review methodology.

SKILL.md

1.8 KB, as published. Nobody here has run it

<essential_principles>

Code Review Philosophy

Reviews exist to:

  1. Catch bugs before production
  2. Share knowledge across the team
  3. Maintain consistency in the codebase

Reviews do NOT exist to:

  • Show off knowledge
  • Enforce personal style preferences
  • Block progress unnecessarily

The 3-Pass Method

Pass 1: Understand (don't comment yet)

  • What is this change trying to do?
  • What files are affected?
  • What's the scope?

Pass 2: Correctness

  • Are there bugs?
  • Are edge cases handled?
  • Are there security issues?

Pass 3: Improvements (max 5 comments)

  • Is it readable?
  • Is it maintainable?
  • Are there better patterns?

Review Checklist

Must Check

  • Tests pass
  • No obvious bugs
  • Edge cases handled
  • No security vulnerabilities
  • No secrets in code

Should Check

  • Code is readable
  • Functions < 50 lines
  • Clear naming
  • Helpful error messages

Nice to Check

  • Performance considerations
  • Documentation updated
  • Consistent patterns

Feedback Style

DO:

  • Ask questions: "What happens if X is null?"
  • Be specific: "Line 42: Consider guard clause"
  • Acknowledge good work: "Nice refactor"
  • Limit comments: Max 5 per review

DON'T:

  • Dictate: "You must do X"
  • Be vague: "This could be better"
  • Nitpick style: "I prefer single quotes" </essential_principles>
<intake> What would you like me to review?
  1. Paste code/diff - I'll review inline
  2. Reference file - Use @filename
  3. Describe PR - I'll ask questions

Context:

  • Bug fix / New feature / Refactor / Performance

Specific concerns? (Security, breaking changes, etc.) </intake>

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.