Public BitDive workflows packaged for agent use.
This repository contains reusable BitDive skills for runtime trace analysis, MCP-driven investigation, service instrumentation, regression management, and developer workflows. It is designed for teams who want to install BitDive guidance into agent environments such as Codex or Claude Code, instead of rewriting prompts and runbooks by hand.
Watch the BitDive product demo on YouTube:
Use this repository when you want agent-ready BitDive workflows for tasks such as:
- adding BitDive to a Spring Boot service
- understanding which MCP tool to call and when
- comparing traces to find behavioral drift
- running phased BitDive development workflows
- repairing or refreshing replay-based regression groups
- connecting Dockerized services to BitDive infrastructure
These workflows are meant to make BitDive usage repeatable, faster, and less prompt-dependent.
The repository ships the same ideas in two formats.
| Path | Purpose |
|---|---|
skills/<skill-name>/SKILL.md |
Portable installable skills for agent ecosystems that support the skills format |
skills/<skill-name>/agents/openai.yaml |
Agent-facing metadata for the portable skill package |
claude/agents/<agent-name>.md |
Native Claude Code subagents |
| Workflow | Purpose |
|---|---|
add-bitdive-spring |
Add BitDive producer and optional replay support to a Spring Boot service |
bitdive-overview |
Choose the right BitDive MCP tool for discovery, inspection, and updates |
bitdive-trace-comparison |
Compare traces and locate the exact point of behavior drift |
bitdive-dev-workflow |
Run a phased BitDive development workflow with human checkpoints |
bitdive-test-management |
Create, wire, repair, refresh, and rebuild replay groups |
bitdive-docker-networking |
Connect Dockerized services to cloud or self-hosted BitDive |
Use the format that matches your agent environment:
- use
skills/if you want one-command install throughnpx skills add - use
claude/agents/if you specifically want native Claude Code agents in.claude/agents/ - workflow names are intentionally aligned across both formats
Install the BitDive portable skills and choose the target agent interactively:
npx skills add bitDive/bitdive-skills --skill '*'Global interactive install:
npx skills add bitDive/bitdive-skills --skill '*' -gInstall the full portable skill set into Codex:
npx skills add bitDive/bitdive-skills --skill '*' -a codexGlobal install:
npx skills add bitDive/bitdive-skills --skill '*' -g -a codexInstall the same portable skill set into Claude Code:
npx skills add bitDive/bitdive-skills --skill '*' -a claude-codeGlobal install:
npx skills add bitDive/bitdive-skills --skill '*' -g -a claude-codeInstall the full portable set into both agents:
npx skills add bitDive/bitdive-skills --skill '*' -a codex -a claude-codeGlobal install:
npx skills add bitDive/bitdive-skills --skill '*' -g -a codex -a claude-codeIf you specifically want native Claude Code subagents rather than the portable skills/ format:
git clone https://github.com/bitDive/bitdive-skills.git
cd bitdive-skills
mkdir -p /path/to/project/.claude/agents
cp claude/agents/<agent-name>.md /path/to/project/.claude/agents/Optional user-wide install:
mkdir -p ~/.claude/agents
cp claude/agents/<agent-name>.md ~/.claude/agents/These workflows are most useful when:
- BitDive MCP is configured and reachable
- the target service is already instrumented or is about to be instrumented
- the repository has a real module-scoped test command that can be rerun quickly
- the team wants repeatable runtime-backed workflows rather than one-off prompts
This repository is intentionally text-first and workflow-oriented.
- the skills are meant to be portable across repositories
- private project names and local-only paths were removed from the public set
- MCP-centered investigation and replay management are the main focus
- each workflow is intended to reduce prompt ambiguity for common BitDive tasks
agents/openai.yamlis included for each portable skill so the set is ready for UI-facing use- Claude support is stored as visible source files in
claude/agents/ - if you want to publish under another license, replace the root
LICENSEfile before pushing the repository
