跳到正文
cccskills
免费在 GitHub 公开

review-code

Review code changes for correctness defects, regressions, security risks, data-integrity problems, concurrency hazards, and missing meaningful tests. Use for pull requests, branches, commits, patches, or working-tree reviews; do not use for implementation unless the user separately requests fixes.

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

查看安装方法

包含的文件(4)

  • SKILL.md2.3 KB
  • agents/openai.yaml224 B
  • references/review-checklist.md1.5 KB
  • references/review-lenses.md1.3 KB

SKILL.md(原文)

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

Review Code

Workflow

  1. Establish the review target and comparison base.
  2. Inspect the diff, then trace changed behavior through callers, contracts, persistence, side effects, and tests.
  3. Inspect the target, isolation, fixtures, and side effects before running a narrow check that materially confirms a suspected issue.
  4. Rank findings by impact and confidence; remove duplicates and speculation.
  5. Return findings first, followed by open questions and a short summary.

Use correctness as the default lens. For large, risky, or requirement-heavy changes, add the standards and specification lenses in references/review-lenses.md. Keep each finding tied to its source; documented rules and acceptance criteria outrank personal preference.

Finding standard

Each finding must include:

  • severity;
  • precise file and line or symbol;
  • the failing scenario or invariant;
  • user or system impact;
  • evidence or a reproduction path;
  • a concise fix direction when clear.

Do not report style preferences, theoretical risks without a reachable path, or issues outside the change unless the diff materially exposes them.

Review boundaries

  • Review in read-only mode by default.
  • Do not run production-integrated, shared-environment, or destructive tests without explicit authorization and verified isolation.
  • Do not modify, comment, approve, or request changes on a remote PR unless asked.
  • Do not equate passing tests with correctness.
  • Do not treat generated code or lockfile churn as a defect without understanding its source.
  • Respect repository-specific compatibility and risk rules.
  • State when a claim was not reproduced.

Checklist

Read references/review-checklist.md when the change touches APIs, data, authorization, concurrency, infrastructure, or tests.

Output

If there are no actionable findings, say so directly and name residual unverified areas. Keep the summary shorter than the findings.

评价

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

评论

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

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

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

0 / 1000 字

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

同一仓库的技能

Build or modify backend APIs, services, jobs, persistence, and integrations while preserving contracts, authorization, data integrity, and failure behavior. Use for server-side features, database changes, background processing, backend defects, and service refactors; do not use for frontend-only or infrastructure-only work.

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

Phelan164/codex-howto142026年10月17日 更新

Build or modify frontend interfaces using repository-native components while preserving accessibility, responsive behavior, state handling, and visual verification. Use for UI features, design implementation, forms, client-side defects, and frontend refactors; do not use for backend-only or infrastructure-only work.

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

Phelan164/codex-howto142026年10月17日 更新

Select the smallest useful Codex engineering workflow from this repository's existing skills. Use when a task spans multiple engineering concerns, the user is unsure which skill to invoke, or loading every specialist would waste context; return a recommendation only and do not execute the engineering task.

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

Phelan164/codex-howto142026年10月17日 更新

Implement a repository code or configuration change through reproduction, focused checks, review, and evidence. Use for end-to-end features and fixes; not for explanation-only, review-only, research, content publishing, or production operations.

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

Phelan164/codex-howto142026年10月17日 更新

Review a small code or documentation change and return only evidence-backed correctness findings. Use in the Codex How To local plugin lab; do not modify files or post remote comments.

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

Phelan164/codex-howto142026年10月17日 更新

Maintain a review-first Markdown knowledge base for Codex practices with source provenance, engineering capture, citation-aware queries, explicit archive and promotion, and deterministic linting. Use when asked to capture a durable engineering lesson, ingest Codex research, query or archive what the repository knows, check wiki health, reconcile conflicting guidance, or promote verified knowledge.

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

Phelan164/codex-howto142026年10月17日 更新

查看 Phelan164 的全部技能

报告此技能的问题