Community程式設計與開發github.com

先調查再行動

在診斷不明確的失敗原因時,先收集證據再修改程式碼。適用於未知原因、間歇性行為、效能回歸或需要證據排序假設的調查。

先調查再行動 是什麼?

「先調查再行動」技能旨在指導 AI 代理在遇到不明確的錯誤或異常行為時,採取一套嚴謹的診斷流程,避免未經充分分析就貿然修改程式碼。此技能強制代理區分觀察到的症狀與推斷出的原因,並系統性地追蹤輸入、狀態轉換、所有權邊界與失敗輸出。代理需根據證據與低成本的反駁價值對假設進行排序,直到找到一個足以解釋所有證據的可信機制為止。此技能支援 Claude Code、Cursor 等命令列或編輯器整合的 AI 代理,特別適合處理間歇性錯誤、效能回歸或需要深入調查的複雜問題。使用此技能時,代理只會報告根本原因與證明,除非任務明確授權,否則不會進行修復。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/JuliusBrussee/caveman/tree/main/skills/investigate-first

Installed? Explore more 程式設計與開發 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

先調查再行動 是做什麼的?

在修改產品程式碼之前,先收集證據。

  • 將觀察到的症狀與推斷的原因分開。
  • 追蹤輸入、狀態轉換、所有權邊界與失敗輸出。
  • 根據證據與低成本的反駁價值對假設進行排序。
  • 在有一個可信機制能夠解釋所有證據之前,不要編輯程式碼。
  • 當證據足以命名原因或明確的阻礙時,停止探索。

報告原因與證明。除非任務授權實作,否則不進行修復。

Individual skills in this repo

This repo contains 12 individual skills — each has its own dedicated page.

JuliusBrussee/caveman-discover

Find and label every LLM workflow in the repository so Caveman Cloud groups spend by workflow instead of one bucket. Use for "discover workflows" or breaking LLM spend down by workflow.

JuliusBrussee/caveman-evidence-review

Read-only review of Caveman Cloud evidence: cost, Cave Score, workflows, traces, latency, errors, routing, savings. Use when asked what Caveman found or where LLM spend goes.

JuliusBrussee/caveman-explore

Read-only repository explorer for cold-start orientation, broad cross-file localization, or when a direct search failed. Skip it when the exact file or symbol is already named. Returns path:line citations only; its reads stay out of main context.

JuliusBrussee/caveman-learn

Act on a Caveman learn report - review the ranked token sinks, apply cost-lowering fixes with per-edit consent, and report what those fixes returned. Use when asked to lower an agent's token cost, what caveman has saved, to trim a heavy CLAUDE.md, or to offload re-pasted context into cavemem.

JuliusBrussee/caveman-manage

Inspect Caveman Cloud's experiment lifecycle and block unsafe execution. Use when asked to start, approve, cancel, promote or roll back a Caveman experiment.

JuliusBrussee/caveman-optimize

Turn a Caveman optimization observation into an operator-chosen candidate with a paired baseline evaluation. Use when asked to inspect or evaluate a Caveman optimization report. Needs explicit approval.

JuliusBrussee/caveman-setup

Wire a repository through the Caveman Cloud gateway so every LLM request is measured, with no behavior change. Use for "set up caveman" or adding LLM spend observability.

JuliusBrussee/lean-build

Build feature work with high overbuilding risk. Use for new behavior, product slices, or integrations where repository reuse, strict scope, and an explicit stop condition matter.

JuliusBrussee/migration

Implement reversible compatibility-safe transitions. Use for schema, data, API, protocol, configuration, or dependency migrations requiring rollback and preservation proof.

JuliusBrussee/safe-refactor

Restructure code while preserving behavior. Use for extraction, consolidation, ownership moves, or cleanup where verification must bracket structural edits.

JuliusBrussee/surgical-patch

Fix bugs and small behavior changes at the narrowest responsible layer. Use when regression proof, preserved surrounding behavior, and task-relevant tests matter.

JuliusBrussee/verify-and-stop

Prove existing work meets acceptance conditions without expanding scope. Use for validation-only tasks, completion checks, focused gate runs, and last-mile proof.

相關技能