security-review
RBAC/監査ログ/秘密情報/マルチテナント越境/LLMプロンプト注入の観点でレビューする。
Découvrez les skills Vie quotidienne, comparez leurs dépôts et consultez leurs instructions.
RBAC/監査ログ/秘密情報/マルチテナント越境/LLMプロンプト注入の観点でレビューする。
Use for Docker/Kubernetes issues. Inspect runtime state and logs before changing images/manifests.
Temporal+LangGraph の工程(step)追加/修正の実装テンプレ。Activity 冪等性、output_path/output_digest、承認待ち、監査ログを含む。
DB管理プロンプトの作成/更新(versioning、variables、レンダリング確認、出力マーカー準拠)に使う。
Use for investigation-heavy work. Prefer tool-driven evidence (search, logs, diffs) before changing code.
Use when integrating multiple LLM providers. Keep provider-specific code isolated behind a small interface.
Use for Next.js design/architecture work. Respect App Router boundaries and server/client separation.
マルチテナント(顧客別DB分離)のDB運用・マイグレーション・調査に使う。
Use when the root cause is unclear. Trace the failure back through the call stack and isolate the first bad state.
Use for React Native / Expo troubleshooting (Metro bundler, native modules, simulator/emulator issues).
Use for LangGraph agent design and refactors. Prefer explicit state, small nodes, and clear transitions.
Use when generating or refactoring UI artifacts. Prefer modular components and consistent styling.
Use when running Codex as an independent reviewer. Focus on actionable, prioritized findings.
Use when answering LangGraph questions. Prefer reading local project code/specs; fetch docs only if needed.
Use for SvelteKit 2 + Svelte 5 + Tailwind v4 projects. Keep SSR/client boundaries and Tailwind config consistent.
Use when you want a second-opinion review from a different model/tool. Provide narrow, reviewable diffs.
Use to review OpenAI API integrations for correctness (endpoints, params, auth, response handling) and robustness.
This skill should be used when the user asks to "run tasks in parallel", "create worktrees", "dispatch parallel agents", "orchestrate execution", or when autonomous-dev needs to execute independent tasks simult...
This skill should be used when the work type is FRONTEND and visual verification is needed. Provides browser automation for screenshot comparison, responsive testing, and interactive element verification using...
This skill should be used when the user initiates autonomous development with /auto, /auto-lite, or similar commands to classify the type of work. Semantic work type classification with multi-layer detection. A...
This skill should be used when the user asks to "resolve merge conflicts", "fix git conflicts", "merge branches", or when autonomous-dev encounters merge conflicts during branch integration. Intelligently resol...
This skill defines the Initializer Agent protocol for the Two-Agent Pattern. The Initializer Agent runs ONCE at the start of a new task to analyze, plan, and set up state for Coding Agents. Use this when starti...
This skill should be used when the user asks to "break down this feature", "decompose this task", "create task list", "plan implementation steps", "identify subtasks", or when planning autonomous execution. Con...
This skill should be used when the user asks to "run verification", "check if code passes", "run tests and lint", "verify implementation", or after code changes in autonomous mode. Runs typecheck, lint, test, a...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.