メニュー
Add new functionality in Codex by mapping existing architecture first, then implementing the smallest compatible change and verifying behavior with focused checks.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Add new functionality by understanding existing patterns and dependencies before writing code. Locates where the feature belongs, studies conventions, implements following precedent, then verifies integration. Use when asked to add a feature, flag, endpoint, component, or module.
Thorough code review using token-efficient context gathering. Analyzes PRs, diffs, or staged changes by checking blast radius, complexity, and dependencies before reviewing the actual code. Use when asked to review a PR, review changes, or do a code review.
Systematically investigate and fix bugs using token-efficient context gathering. Reproduces the issue first, localizes with blame and history, traces the call path, then verifies the fix. Use when asked to fix a bug, investigate an error, or debug unexpected behavior.
Diagnose and fix performance issues by measuring before optimizing. Establishes baselines, identifies bottlenecks through call graphs and complexity analysis, then confirms improvements with numbers. Use when asked to optimize, speed up, reduce memory usage, or fix slowness.
Efficiently explore and understand an unfamiliar codebase using token-lean context gathering. Maps project structure, identifies key files, and builds understanding progressively without reading everything. Use when onboarding to a new project, asked to understand a codebase, or starting work in unfamiliar code.
Migrate frameworks, APIs, or language versions incrementally with verification at each step. Surveys the migration surface, batches work by dependency order, and commits after each verified batch. Use when asked to migrate between frameworks, upgrade major versions, or adapt to new API versions.
| name | add-feature |
| description | Add new functionality in Codex by mapping existing architecture first, then implementing the smallest compatible change and verifying behavior with focused checks. |
| compatibility | Codex CLI with terminal access, Node.js >=18, git (tokenlean CLI optional) |
Add functionality by understanding existing code paths before editing.
Locate -> Understand -> Implement -> Integrate -> Verify
rg --files
rg -n "<feature keyword>" src bin test
Find:
bin/, routing, handlers)sed -n '1,220p' <target-file>
rg -n "export |function |class " <target-file>
rg -n "<target symbol>" src test
If available, tokenlean shortcuts:
tl-symbols <target-file>
tl-deps <target-file>
tl-exports <target-file>
bin/tl-*.mjs.rg -n "<new symbol|flag|option>" src bin test
Check:
npm test
node bin/<changed-tool>.mjs --help
Use narrower checks first when possible (single test file or targeted command), then broader checks.