Menu
Code readability review. Do NOT use for security (use-context-reviewer-security), error handling (use-context-reviewer-silence), or test design (use-context-reviewer-testability).
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
issue が build に投入できる形かを検分し、verdict (build-ready / needs-plan / needs-fix) と指摘を返す。起票には使わない (/issue)。PR のスクリーニングには使わない (/preview)。
Inspect whether an issue is in shape to hand to build, returning a verdict (build-ready / needs-plan / needs-fix) and the findings. Do NOT use to file an issue (use /issue) or to screen a PR (use /preview).
critic-design による敵対的批判を伴う設計探索。生き残った案を構造化 plan にまとめ、自己点検して呼び出し元に返す。plan の永続先は issue の Plan 節が唯一。計画意図のないコードベース調査には使わない (代わりに /research)。
Design exploration with adversarial critique by critic-design. Assembles the surviving approach into a structured plan, self-checks it, and returns it to the caller. The issue's Plan section is the plan's only persistent home. Do NOT use for codebase investigation without planning intent (use /research instead).
構造化されたタイトルと本文で GitHub Issue を生成する。単独で成立し、前段を要求しない。challenge / research の成果物が会話にあれば本文の根拠に使い、/think の plan 下書きがあれば `## Plan` 節へ移設する。issue 番号を渡すと、起票済みで Plan 節を持たない issue へ plan を転記する。
Generate GitHub Issue with structured title and body. Standalone; requires no upstream stage. When challenge / research artifacts exist in the conversation, they feed the body's evidence; when a /think plan draft exists, it is transferred into the `## Plan` section. Given an issue number, it transfers a plan into a filed issue that has no Plan section.
| name | use-context-reviewer-readability |
| description | Code readability review. Do NOT use for security (use-context-reviewer-security), error handling (use-context-reviewer-silence), or test design (use-context-reviewer-testability). |
| when_to_use | 可読性, 明確, 命名, 変数名, 関数名, ネスト, 関数設計, コメント, 複雑, Miller's Law, ミラーの法則, 認知負荷, AI-generated, 過剰設計 |
| allowed-tools | Read Task Bash(ugrep:*) Bash(bfs:*) |
| agent | reviewer-readability |
| context | fork |
| background | false |
| user-invocable | false |
Thresholds are based on cognitive limits such as working memory and one-screen focus, and established metrics such as McCabe complexity.
| Target | Recommended | Why |
|---|---|---|
| Function lines | ≤30 | One-screen readability |
| File lines | ≤400 | Module-level cognitive ceiling |
| Nesting depth | ≤3 | Branch tracking within working memory |
| Function arguments | ≤3 | Argument order memorization limit |
| Cyclomatic complexity | ≤10 | McCabe 1976: testable without path explosion |
| ID | Pattern | Fix |
|---|---|---|
| RD1 | Vague processData() | validateUserEmail() |
| RD1 | Misleading identifiers | Names reveal intent |
| RD2 | Nesting > 3 levels | Guard clauses, extract functions |
| RD2 | Function > 30 lines | Decompose |
| RD3 | Comment: // increment i | Delete; self-evident |
| RD3 | Comment: // TODO: fix later | Create issue or fix now |
| RD4 | Interface for single impl | Remove until 2nd impl |
| RD4 | Class for stateless logic | Pure function |
| RD5 | > 5 function parameters | Config object or decompose |
| Topic | File |
|---|---|
| Control Flow | ${CLAUDE_SKILL_DIR}/references/control-flow.md |
| Comments | ${CLAUDE_SKILL_DIR}/references/comments-clarity.md |
| AI Antipatterns | ${CLAUDE_SKILL_DIR}/references/ai-antipatterns.md |
| Naming | ${CLAUDE_SKILL_DIR}/references/naming.md |
