メニュー
Config, env, wrangler review. USE WHEN: user runs /review-configuration or explicitly asks for this review. DO NOT USE WHEN: implementing features or fixing bugs unless the user asked for a review.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/louisbrulenaudet/monorepo-template --skill review-configurationコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
USE WHEN: editing Cursor/Claude agent config, rules, hooks, skills, MCP, subagents, slash commands, or dual-tree sync; or when asking how Claude vs Cursor instructions are laid out in this monorepo. DO NOT USE WHEN: implementing app features, Workers, or frontend UI unless the task is specifically about agent tooling.
pnpm workspace and dependency management for this monorepo. Triggers on: pnpm install, pnpm add/remove/update, workspace protocol, catalogs, filtering, lockfile, hoisting, allowBuilds, minimumReleaseAge, CI install failures, and dependency version drift. Use when user or agent: adds/removes packages, scaffolds workspace packages, debugs install/hoisting issues, updates shared tool versions, or changes pnpm-workspace.yaml.
Architecture-focused monorepo review. USE WHEN: user runs /review-architecture or explicitly asks for this review. DO NOT USE WHEN: implementing features or fixing bugs unless the user asked for a review.
SOC 職業分類に基づく
| name | review-configuration |
| description | Config, env, wrangler review. USE WHEN: user runs /review-configuration or explicitly asks for this review. DO NOT USE WHEN: implementing features or fixing bugs unless the user asked for a review. |
| disable-model-invocation | true |
Run a configuration-focused review: environment and secrets handling, Cloudflare/wrangler setup, TypeScript and OXC configs, Vite and Wrangler configuration, build modes, and dev/staging/prod parity. Your reply must be a plan of suggested changes: concise, actionable, and structured-not only prose.
Text after the slash command is additional scope/focus - narrow the review accordingly. If none given, use the default scope described below.
.dev.vars (workers) and wrangler env; document required vars in .dev.vars.example.import.meta.env, e.g. VITE_* if used); server-only secrets and config in Workers; build modes (development/production) consistent across tools.@repo/typescript-config (strict.json core → runtime presets); per-package tsc --noEmit via Turborepo transit (no root solution / project references); no conflicting compiler options between packages.front-app assets (SPA) and worker-api worker entry configured correctly.Align with root AGENTS.md and app AGENTS.md for stated config and port allocation.
Conduct a configuration-only review. Inspect the following and call out violations or improvements.
.env* or import.meta.env usage in apps/front-app/src/, apps/worker-api/src/..dev.vars is gitignored; .dev.vars.example lists every required variable with placeholder or description (no real secrets). Wrangler vars and [env.*.vars] only for non-secret config; secrets only in wrangler secret or .dev.vars. No secrets in client-bundled code; only intentionally exposed env keys via Vite (document which prefixes are safe).compatibility_date is set and reasonably current. Flags (e.g. nodejs_compat) are intentional and documented if non-default. front-app: SPA/static assets configuration (e.g. assets, not_found_handling) matches Vite build output. worker-api: dev port (e.g. 8725) matches AGENTS.md; production env and routes match deployment.@cloudflare/vite-plugin); build target and chunk strategy; no dev-only options in production build. Local dev parity with deployed behavior where relevant.strict.json, library.json, workers.json, vite-react.json, vite-node.json), apps/front-app/tsconfig.json + tsconfig.app.json / tsconfig.node.json, apps/worker-api/tsconfig.json, packages/dtos-common/tsconfig.json, packages/enums-common/tsconfig.json.@repo/typescript-config where appropriate. strict enabled via strict.json inheritance. No root solution tsconfig.json and no TypeScript Project References - check-types is tsc --noEmit with Turborepo transit. Worker apps set compilerOptions.types for worker-configuration.d.ts. React apps use split layout: vite-react.json for src/**, vite-node.json for vite.config.ts. Presets keep isolatedDeclarations off (schema-first z.infer in @repo/dtos-common). erasableSyntaxOnly on - no export enum; use as const objects in @repo/enums-common. Each package running check-types declares typescript in devDependencies..oxlintrc.json; no disabled rules that hide real issues without a reason. Ignore patterns exclude build outputs and generated files. No Prettier (or other formatter) in use to avoid conflicts.build uses production mode (e.g. NODE_ENV=production or equivalent). Dev and build use same Node version (engines field). Lockfile is committed; CI uses --frozen-lockfile. packageManager in package.json matches pnpm version. pnpm policy in pnpm-workspace.yaml is intentional and documented..dev.vars.example; required env vars not documented.any encouraged by config.assets / SPA settings mismatch..oxfmtrc.json and .oxlintrc.json; format/lint rules and ignore patterns..oxfmtrc.json and .oxlintrc.json reviewed@file for config files (wrangler.jsonc, vite.config.ts, tsconfig.json, .oxfmtrc.json, .oxlintrc.json).@code for env or config snippets when suggesting changes.@docs for Cloudflare/OXC/TypeScript when checking correct options.If context is insufficient, suggest which config files or @ references to add.
Respond with a plan only (no implementation unless the user asks):
For each item: what to change, where (file/area), and why. If a sub-area has no findings, state it in one line.