Caveman

What you can ask

• Use Caveman to simplify this coding taskCopy

  · Cavecrew skill

• Review this implementation with the Caveman workflow
• Turn this requirement into a compact execution plan

Skills

20 in the ChatGPT listing

• CavecrewUse when a coding task should be delegated to a focused investigator, small-change builder, or diff reviewer so the main context stays compact.
• CavemanUse when the user asks to run or coordinate a Caveman workflow for reducing LLM cost, inspecting workflow evidence, or optimizing agent usage.
• Caveman CommitUse when the user asks for a concise Conventional Commit message or wants a commit message compressed to the change intent.
• Caveman CompressUse when the user explicitly asks to compress a memory, instructions, or todo file into Caveman format while keeping a readable backup.
• Caveman DiscoverUse when the user asks to discover or label LLM workflows in a repository so Caveman can attribute spend by workflow.
• Caveman Evidence ReviewUse when the user asks what Caveman found about LLM cost, traces, latency, errors, routing, savings, or workflow evidence.
• Caveman ExploreUse when a repository needs broad read-only exploration for orientation or localization and the exact file or symbol is not already known.
• Caveman HelpUse when the user explicitly asks for Caveman help, available modes, skills, commands, or a quick-reference summary.
• Caveman LearnUse when the user asks to reduce an agent workflow's token cost, review Caveman savings, trim heavy context files, or act on a Caveman learning report.
• Caveman ManageUse when the user explicitly asks to start, approve, cancel, promote, or roll back a Caveman experiment.
• Caveman OptimizeUse when the user asks to inspect or evaluate a Caveman optimization report before explicitly approving any optimization action.
• Caveman ReviewUse when the user asks for a focused review of a code diff or change using the Caveman workflow.
• Caveman SetupUse when the user explicitly asks to configure Caveman for a repository, workspace, or cloud-backed workflow.
• Caveman StatsUse when the user asks for Caveman usage, cost, savings, score, or workflow statistics from available Caveman evidence.
• Investigate FirstUse when a bug or unexpected behavior needs evidence and a credible root cause before any code is edited.
• Lean BuildUse when implementing a feature or change and the work should be reduced to the smallest coherent, testable slice.
• MigrationUse when planning or implementing a migration that must preserve data, support rollback, and move through reversible transition steps.
• Safe RefactorUse when restructuring code while preserving observable behavior and proving the refactor with tests or other evidence.
• Surgical PatchUse when a narrow regression or defect should be fixed at the responsible layer while preserving surrounding behavior and proving the patch with focused tests.
• Verify and StopUse when a change appears complete and the next step is to run only the relevant proof, report the result, and stop without unrelated cleanup.