Menu
Review a draft text (message, report, PR description, commit message, etc.) from the reader's perspective and suggest improvements.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | ai-review |
| description | Review a draft text (message, report, PR description, commit message, etc.) from the reader's perspective and suggest improvements. |
The user will provide a draft text to review. If no text is provided as an argument, ask them to paste it.
Review the draft across the following dimensions and produce structured feedback:
Produce output in three sections:
Summary — One sentence describing the overall state of the draft (e.g., "Clear structure but missing a deadline and the opening buries the key request.").
Issues — A numbered list of specific problems found, each with:
Revised Draft — A revised version of the full text incorporating all suggestions. Wrap it in a markdown block so the user can copy it cleanly.
Intent-Driven Development (IDD) に基づき、ADR（Architecture Decision Record）形式の Intentドキュメントを作成するスキル。ユーザーの「こういう機能を作りたい」「この設計判断をした」 という意図をWhy/Whatに整理し、How（実装詳細）の混入を検出・分離して、docs/adr/ に連番の ADRファイルを生成する。 このスキルは以下の場合に必ず使用すること： - ユーザーが /intent と入力したとき - 「ADRを書きたい」「意図を記録したい」「intentを作成」「設計判断を残したい」「ADR作って」 「決定を記録」「なぜこうしたか残しておきたい」などと言ったとき - ユーザーが新機能やアーキテクチャの判断について議論し、それを文書化したいと示唆したとき Do NOT trigger for: バグ修正の記録、ルーチンなリファクタリング、意図が自明な些細な変更。
Automatically generate PR descriptions according to project templates.
Structured 5W1H completeness checker for written communication. Analyzes text using a Who/What/When/Where/Why/How framework, produces a status table for each element, and provides concrete rewrite suggestions for missing information. ALWAYS use this skill when the user shares text and asks you to review it, check it, proofread it, or confirm it's ready to send — including progress reports, daily standups, meeting minutes, incident reports, handoff documents, status updates, client emails, Slack messages, PR descriptions, or any prose meant to inform others. Also trigger when the user says things like "これで大丈夫か", "情報足りてるか", "抜けてないか", "伝わるかな", "5W1H", "check if anything is missing", "is this clear enough", "review before sending", or asks you to check whether a written message has enough context for the reader. This skill adds a structured framework that generic reviewing lacks — do not skip it just because you could review text without it. Do NOT trigger for: code review, security review, grammar/style-only che
Safely add a new dotfile to chezmoi management, determining the correct prefix and committing the result.
Scan chezmoi source files for accidentally exposed secrets and verify sensitive files have the private_ prefix.
Inspect the current chezmoi sync state and report unapplied changes, unmanaged files, and whether it is safe to run chezmoi apply.
