メニュー
Use before multi-file, unfamiliar, public-contract, or shared-behavior code changes to build a bounded impact set without reading the whole repository or editing from a single file view.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | codebase-impact |
| description | Use before multi-file, unfamiliar, public-contract, or shared-behavior code changes to build a bounded impact set without reading the whole repository or editing from a single file view. |
Use map -> slice -> expand -> impact set -> delta review.
Use fast search, file lists, project rules, symbols, routes, and related tests. Avoid full-repo reads and generated/vendor files.
Read likely edit files, same-pattern implementations, related tests, and relevant config. Start small, usually 3-8 files.
Expand only when contracts, callers, tests, security/data boundaries, or project rules require it.
Use when the user asks for best practices, broader validation, GitHub/open-source comparison, official-doc verification, or warns against one-sided thinking. Also use before implementation when official API, framework, or project-pattern facts are needed to avoid rework.
Use for review, PR review, audit, self-review, and regression-risk work. Prioritizes bugs, regressions, missing tests, architecture drift, redundancy, security risk, and verification gaps.
Route non-trivial coding work across target-state implementation, codebase impact, Superpowers, Context7, security review, PR workflow, and verification. Skip for tiny edits or simple reads.
Use before finalizing non-trivial design, architecture, configuration, or implementation decisions. Reduces sycophancy bias by independently evaluating proposals, surfacing risks, and presenting alternatives. Auto-triggers on design_or_config and complex_feature routes.
Use before architecture, configuration, workflow, dependency, or high-impact implementation decisions to align goals, constraints, options, tradeoffs, recommendation, acceptance criteria, and user confirmation. Skip for tiny obvious tasks.
Use for non-trivial code changes after the plan is confirmed. Enforces target-state implementation: minimal necessary scope, existing patterns, no avoidable MVP residue, no duplicate logic, synchronized callers/tests/types/errors/config, and verification.
