メニュー
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/agents --skill codebase-reconコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
This skill should be used when the user asks to "complete a branch", "merge to main", "finish my feature", "ship this branch", "integrate to main", "create a PR from GitButler", or when `--complete-branch` flag is mentioned. Guides completion of GitButler virtual branches with safety snapshots, integration workflows, and cleanup.
This skill should be used when coordinating multiple AI agents working concurrently, handling agent handoffs, transferring commits between agents, or when "multi-agent", "concurrent agents", "parallel agents", "agent collaboration", or "parallel execution" are mentioned with GitButler. Provides virtual branch patterns for parallel execution without coordination overhead.
This skill should be used when creating stacks, dependent branches, or when "stack", "stacked branches", "anchor", "--anchor", "but branch new -a", "create dependent branch", or "break feature into PRs" are mentioned with GitButler. Covers anchor-based stacking for dependent features and reviewable PR breakdown.
SKILL.md を表示中
SOC 職業分類に基づく
| name | codebase-recon |
| 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.0"} |
Evidence-based investigation → findings → confidence-tracked conclusions.
outfitter:patterns skilloutfitter:find-root-causes skilloutfitter:report-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):
outfitter:patternsoutfitter:find-root-causesoutfitter:report-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):
outfitter:patterns — extracting and validating patternsoutfitter:find-root-causes — systematic problem diagnosisoutfitter:report-findings — multi-source research synthesisLocal references:
Related skills:
outfitter:pathfinding — clarifying requirements before analysisoutfitter:debugging — structured bug investigation