Coding standards, frameworks, refactoring, and code review (16.9K skills)
Recall project knowledge, past decisions, failures, and preferences when they can help a coding task. Capture changed files before responding.
The English summary is being prepared. Showing the original description.
Codexへの単発の相談・調査・診断依頼を、ハング防止(watchdog)付きで実行する。反復・収束判定・コミットゲートは持たない。行き詰まって一回だけCodexに相談・調査を依頼したいときに使う。コミット前のレビュー収束が目的ならcodex-review-loopを使う。
The English summary is being prepared. Showing the original description.
公開CLIツールのリリース作業(バージョン付け・利用者向けドキュメント・CHANGELOG・検証・PR・タグ)を、ツール公開手順の規約に従って進める。ツールをリリースするとき、バージョンを上げて公開するとき、リリースPRやタグを作るときに使用する。
The English summary is being prepared. Showing the original description.
CLIツール・スクリプトの実行や性能計測を始める前に必ず起動する規律。推測起動・投げっぱなし・既知の失敗の再発・上限なしの待ち続けを防ぐ。ツールやスクリプトを実行して結果を検証するとき、ベンチマーク・性能計測をするとき、性能対策の前後比較を取るとき、実行や計測が長引いて止まらないときに使う。
The English summary is being prepared. Showing the original description.
opus-reviewer(Opusモデル、read-only)にレビューさせ、各指摘を実コードで検証して修正/反証/受容/保留に仕分け、再レビューを反復する。未解決ゼロ・千日手・要ユーザー判断のいずれかで終了。Opusモデルでコードレビューを回したいときに使う。
The English summary is being prepared. Showing the original description.
反復レビュー・ループ(codex-review-loop・fable-review-loop・opus-review-loop)が共有する判断ロジックの正本。起動可否ゲート・レビュアーの正体に依存しない大前提・常設観点・レビュー依頼に含める内容と含めてはならない内容・照合仕分け・終了判定・報告を定義する。内部専用でユーザーが直接使うものではない。
The English summary is being prepared. Showing the original description.
fable-reviewer(Fableモデル、read-only)にレビューさせ、各指摘を実コードで検証して修正/反証/受容/保留に仕分け、再レビューを反復する。未解決ゼロ・千日手・要ユーザー判断のいずれかで終了。Fableモデルでコードレビューを回したいときに使う。
The English summary is being prepared. Showing the original description.
gitコミットをcommit-workerエージェントに委譲して実行する。コミットの依頼を受けたとき、変更をコミットするときに使用する。
The English summary is being prepared. Showing the original description.
codex:codex-rescueエージェントを起動する各スキル(codex-review-loop・codex-consult等)が共有する、ハング防止付きの起動・監視・再試行契約の正本。内部専用でユーザーが直接使うものではない。
The English summary is being prepared. Showing the original description.
codex:rescueにレビューさせ、各指摘を実コードで検証して修正/反証/受容/保留に仕分け、再レビューを反復する。未解決ゼロ・千日手・要ユーザー判断のいずれかで終了。コードレビューを回したいときに使う。
The English summary is being prepared. Showing the original description.
Separates signal from noise in metrics you cannot observe directly, updating a belief from evidence instead of reacting to the latest reading - Bayesian updates over competing explanations, and a filter that says whether this week's move is real. Use when a metric moves and someone wants to act, when diagnosing why traffic or revenue changed, when a dashboard number contradicts intuition, or when deciding whether a trend is real yet.
The English summary is being prepared. Showing the original description.
Draft a pull request description from the current branch diff plus rolling-wave project context. Use when the user wants PR body text, changes, potential risks, or reviewer notes for a branch, especially after completing a rolling-wave slice. Defaults to the Git Town parent branch when no base branch is named.
The English summary is being prepared. Showing the original description.
Review changed code for YAGNI, removable over-complexity, reuse, code quality, and efficiency, then apply worthwhile simplifications. Use when the user asks to simplify, clean up, tighten, de-hack recent changes, identify logic that can be dropped, or review whether added safeguards and edge-case handling are actually needed.
The English summary is being prepared. Showing the original description.
Review local git changes before opening a PR or merging. First review all local tracked and untracked files; if none exist, review the current branch against a requested base branch or the Git Town parent branch. Use zero to three review subagents only when risk, diff size, language specificity, or uncertainty justifies the token cost, then report high-confidence bugs, regressions, risky assumptions, and missing tests. Use when the user asks for code review, local review, branch sanity check, pre-PR review, or review of work-in-progress changes.
The English summary is being prepared. Showing the original description.
Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says 'debug this', 'why is this failing', 'fix this bug', 'trace this error', or pastes stack traces, error messages, or issue references.
The English summary is being prepared. Showing the original description.
Create a git branch named after a GitHub issue.
The English summary is being prepared. Showing the original description.
Explains code in plain language for someone unfamiliar with the programming language. Use when asked to explain code, walk through logic, describe what a function does, or when the user says "explain this" or "walk me through this".
The English summary is being prepared. Showing the original description.
Generate a conventional commit message for the current staged git changes. Use when the user wants to commit, asks for a commit message, or asks what to write for a commit.
The English summary is being prepared. Showing the original description.
Apply frontend code quality rules for React and TypeScript components. Auto-activates when editing component files.
The English summary is being prepared. Showing the original description.
API design conventions for this codebase. Use whenever writing or reviewing API endpoints, route handlers, or HTTP clients.
The English summary is being prepared. Showing the original description.
Review database migration files for naming conventions and dangerous operations. Auto-activates for migration files.
The English summary is being prepared. Showing the original description.
Rename a code symbol (variable, function, class) across a specified scope.
The English summary is being prepared. Showing the original description.
Review code against a standard checklist covering security, correctness, performance, and readability. Use when asked to review code, check a PR, or audit changes.
The English summary is being prepared. Showing the original description.
Summarizes uncommitted git changes and flags anything risky. Use when the user asks what changed, wants a commit message draft, or asks to review their diff before committing.
The English summary is being prepared. Showing the original description.