跳到正文
cccskills
免费在 GitHub 公开

code-review

Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedback has arrived and needs acting on, or when feedback seems wrong and needs a reasoned response rather than compliance.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md2.1 KB

SKILL.md(原文)

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

Code review

Two directions, one skill: reviewing, and being reviewed.

Reviewing

Read the diff against what the change is for, not against your preferences. Order matters — spend attention where damage is expensive:

  1. Correctness — does it do what it claims, including at the boundaries and on the error path?
  2. Blast radius — what else consumes this? Signature and schema changes are the ones that break things far away.
  3. Security and data — untrusted input, authorization, anything logged or persisted.
  4. Tests — do they pin the new behavior, or do they pass regardless?
  5. Design — will this shape hold under the next change?
  6. Style — last, and only where a linter cannot.

Say which category each comment is, and whether it blocks. A review that mixes a data-loss bug with a naming preference in one undifferentiated list wastes the author's judgment.

Receiving

Feedback is a report of a reader's experience, and that part is always valid — if the reviewer misread it, the code is misleading. The proposed remedy is a separate thing and may be wrong.

  • Verify before implementing. A suggestion that would break behavior gets a reply, not a commit.
  • Disagreeing is fine; ignoring is not. Answer every comment: changed, or why not.
  • Do not batch-accept. Applying every suggestion without judgment is how good code becomes incoherent.
  • Where a reviewer is factually wrong, show the evidence — the test, the spec, the failing case — rather than asserting.

Never

  • Approve your own work, or a change you authored under another name.
  • Leave a blocking comment without saying what would unblock it.
  • Rewrite the author's approach in a review comment. Propose it, and let them decide.

评价

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

评论

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

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

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

0 / 1000 字

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

同一仓库的技能

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20762026年10月19日 更新

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20762026年10月19日 更新

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20762026年10月19日 更新

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20762026年10月19日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20762026年10月19日 更新

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20762026年10月19日 更新

查看 cbrock84 的全部技能

报告此技能的问题