メニュー
This skill should be used when analyzing codebases, understanding architecture, or when analyze, investigate, explore code, or understand architecture are mentioned.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/outfitter-dev/outfitter --skill codebase-analysisコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Patterns for @outfitter/daemon including lifecycle management, IPC communication, health checks, and PID files. Use when building background services, daemons, or when "daemon", "IPC", "health check", "background service", or "@outfitter/daemon" are mentioned.
Creates handlers, CLI commands, MCP tools, and daemon services following Outfitter Dev Kit conventions. Use when adding new components to a project, scaffolding code, or when "create handler", "new command", "add tool", or "daemon service" are mentioned.
Deep patterns for @outfitter/mcp including tool registration, Zod schemas, resources, and server configuration. Use when building MCP servers, registering tools, defining resources, or when "MCP server", "MCP tool", "registerTool", or "@outfitter/mcp" are mentioned.
SKILL.md を表示中
SOC 職業分類に基づく
| name | codebase-analysis |
| description | This skill should be used when analyzing codebases, understanding architecture, or when analyze, investigate, explore code, or understand architecture are mentioned. |
| metadata | {"version":"1.0.1"} |
Evidence-based investigation → findings → confidence-tracked conclusions.
find-patterns skillfind-root-causes skillreport-findings skill<when_to_use>
NOT for: wild guessing, assumptions without evidence, conclusions before investigation
</when_to_use>
| Bar | Lvl | Name | Action |
|---|---|---|---|
░░░░░ | 0 | Gathering | Collect initial evidence |
▓░░░░ | 1 | Surveying |
| Broad scan, surface patterns |
▓▓░░░ | 2 | Investigating | Deep dive, verify patterns |
▓▓▓░░ | 3 | Analyzing | Cross-reference, fill gaps |
▓▓▓▓░ | 4 | Synthesizing | Connect findings, high confidence |
▓▓▓▓▓ | 5 | Concluded | Deliver findings |
Calibration: 0=0–19%, 1=20–39%, 2=40–59%, 3=60–74%, 4=75–89%, 5=90–100%
Start honest. Clear codebase + focused question → level 2–3. Vague or complex → level 0–1.
At level 4: "High confidence in findings. One more angle would reach full certainty. Continue or deliver now?"
Below level 5: include △ Caveats section.
Evidence over assumption — investigate when you can, guess only when you must.
Multi-source gathering — code, docs, tests, history, web research, runtime behavior.
Multiple angles — examine from different perspectives before concluding.
Document gaps — flag uncertainty with △, track what's unknown.
Show your work — findings include supporting evidence, not just conclusions.
Calibrate confidence — distinguish fact from inference from assumption.
<evidence_gathering>
Start broad, then narrow:
Layer evidence:
Follow the trail:
</evidence_gathering>
<output_format>
After each evidence-gathering step emit:
{ numbered list of discoveries with supporting evidence }
{ recurring themes or structures identified }
{ what findings mean for the question at hand }
Overall: {BAR} {PERCENTAGE}%
High confidence areas:
Lower confidence areas:
Assumptions:
Gaps:
Unknowns:
</output_format>
<specialized_techniques>
Load skills for specialized analysis (see Steps section):
find-patternsfind-root-causesreport-findings</specialized_techniques>
Loop: Gather → Analyze → Update Confidence → Next step
At each step:
Before concluding (level 4+):
Check evidence quality:
Check completeness:
Check deliverable:
ALWAYS:
NEVER:
Core methodology:
Micro-skills (load as needed):
find-patterns — extracting and validating patternsfind-root-causes — systematic problem diagnosisreport-findings — multi-source research synthesisLocal references:
Related skills:
pathfinding — clarifying requirements before analysisdebugging — structured bug investigation