本文へ移動
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(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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-howto132026年10月10日 更新

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-howto132026年10月10日 更新

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-howto132026年10月10日 更新

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-howto132026年10月10日 更新

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-howto132026年10月10日 更新

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-howto132026年10月10日 更新

Phelan164 のスキルをすべて見る

このスキルの問題を報告する