القائمة
This skill should be used when the user asks for "code review", "レビューして", "review this diff", "実装をレビュー", or wants rigorous review of recently created artifacts.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
This skill should be used when the user asks to "lint AI assistant config", "check AGENTS.md", "validate SKILL.md", "agnix lint", or wants to detect and fix best-practice violations in Claude Code / agent configuration files.
This skill is the mandatory reference for all Claude Code hook creation. Use cc-hooks-ts for every hook. This skill should be used when the user asks to "create a hook", "add a hook", "write a hook", "implement a hook", "rewrite hooks in TypeScript", "use cc-hooks-ts", or needs to build any Claude Code hook — cc-hooks-ts is always required regardless of whether explicitly mentioned.
Auto-activate CCS CLI delegation for deterministic tasks. Parses user input, auto-selects optimal profile (glm/kimi/custom) from ~/.ccs/config.json, enhances prompts with context, executes via `ccs {profile} -p "task"` or `ccs {profile}:continue`, and reports results. Triggers on "use ccs [task]" patterns, typo/test/refactor keywords. Excludes complex architecture, security-critical code, performance optimization, breaking changes.
This skill should be used when the user asks to "handoff from CCS", "Claude Codeの作業を引き継ぐ", "rate limit handoff", "context overflow", or wants to resume interrupted work from another CCS profile session.
Direct utility reference for code-review PR scripts. Documents unresolved-thread, comment, CI-status, and CI-log helpers used by higher-level PR workflows.
This skill should be used when the user asks to "organize commits", "split this diff into commits", "コミットを整理", "レビューしやすいコミット", or wants current changes grouped into logical commits.
| name | code-review:code-review |
| description | This skill should be used when the user asks for "code review", "レビューして", "review this diff", "実装をレビュー", or wants rigorous review of recently created artifacts. |
Review the recently created artifacts to identify issues and fix them.
Important: No leniency is tolerated. Conduct code review with strict self-reflection and zero compromises.
$ARGUMENTS
Identify review target files by combining the following information sources:
Check progress files
.md file in the .agents/progress/ directory.jsonl) to identify edited filesCheck git diff
git diff --name-only and git diff --staged --name-only to retrieve changed filesFiles specified as arguments (if provided)
Launch the following 5 agents in parallel to conduct reviews from different perspectives:
design-reviewer — Design and architecture (single responsibility, circular dependencies, tight coupling)implementation-reviewer — Implementation quality (readability, naming, duplicate code, functional style)type-safety-reviewer — Type safety (any type prohibition, proper type definitions)ai-antipattern-reviewer — AI antipatterns (hallucinated APIs, fallback abuse, dead code)goal-validator — Goal achievement (cross-reference progress file with changes)Fix all issues found by the agents directly in the local codebase. Do not comment on the PR.
After all fixes are complete:
git diff to verify changes are correct