Use whenever SQL, ORM/jOOQ code, schema or migrations, indexes, N+1, or database load are in play, even without the word "review" — delegates the performance review of the current branch diff to the sql-performance-reviewer agent.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
レビュー本体は専任サブエージェント sql-performance-reviewer。あなたは対象の確定 → 起動 → 中継だけ。
git merge-base <default> HEAD から HEAD + 作業ツリー（staged / unstaged / 未追跡）。<default> は git symbolic-ref refs/remotes/origin/HEAD（無ければ main → master の順で存在確認）。既定ブランチ上にいるなら作業ツリーだけ。git diff <base> --stat、git status --short。
SQL 関連 = .sql・スキーマ・マイグレーション・ORM / クエリビルダの呼び出し・SQL 文字列・接続やプールの設定。明白に無ければその旨を報告して終える。迷ったら起動する。sql-performance-reviewer を起動（バックグラウンド可）。渡すのは: ルートの絶対パス、基点 SHA とブランチ名、作業ツリーも対象、変更ファイル一覧。diff 全文は貼らない。No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when adding or changing REST endpoints or the OpenAPI contract — deriving endpoints from the Lean commands and views, writing documents/codebase/openapi.yaml first, then regenerating the backend controller interfaces and the frontend client.
The English summary is being prepared. Showing the original description.
Use after a backend build succeeds or whenever authentication, authorization, actor/identity handling, external service calls (IdP, JWKS, DB, clock), logging, observability, configuration or error contracts are in play — delegates to the backend-design-reviewer agent for a design-quality review of the current branch.
The English summary is being prepared. Showing the original description.
Use when it is time to make the backend follow the Lean model — regenerate Kotlin from Lean, implement the generated interfaces (UseCase, QueryService, Repository, Entity), wire every generated contract test, make the build green, then run the design and SQL reviews. Backend comes after the human confirmed the screens.
The English summary is being prepared. Showing the original description.
Use when you need the current position in the Lean spec-driven pipeline, or any deterministic check of a Cradle project — status, golden regression, Lean layer walls, regeneration impact, unslop lint, ddd cleanup. Runs the scripts under scripts/ and reports their output verbatim.
The English summary is being prepared. Showing the original description.
Use to start a new product on Cradle or to add the Cradle skeleton to an existing repository — writes cradle.json, the project-facts instruction (.apm/instructions/project.instructions.md), documents/{ddd,ai-notes,infra-design,codebase} templates, CI, and a compiling Lean executable-spec scaffold with a minimal example domain, mockup and CLI.
The English summary is being prepared. Showing the original description.
Use when the product owner asks where the project stands, what to do next, or which phase of the Lean spec-driven pipeline is current — runs cradle status and proposes exactly one next step.
The English summary is being prepared. Showing the original description.