ClawTeam Local Development

This skill is for developing and validating ClawTeam inside the ClawTeam repository. Use it when the task is about changing ClawTeam itself, testing local behavior, or verifying multi-agent workflows against the current checkout.

Development Bootstrap

Standardize the local development environment with the bootstrap script:

bash scripts/bootstrap_clawteam_dev.sh

This script lives in scripts/bootstrap_clawteam_dev.sh inside this skill folder.

This script does all of the following:

• Creates a fixed uv environment at ~/.clawteam-venv
• Installs the current repository into that environment with dev dependencies
• Writes ~/.local/bin/clawteam to point at the fixed environment
• Adds a clawteam() shell function block to ~/.bashrc

After it finishes:

source ~/.bashrc
clawteam --version

Use this bootstrap whenever you want the same clawteam command across different Python environments on the machine.

Project Skill Wiring

To wire another local project so its ./.agents and ./.claude directories use this repository's local ClawTeam skills directly:

bash scripts/link_local_clawteam_skills.sh /path/to/project

This script lives in scripts/link_local_clawteam_skills.sh inside this skill folder.

This creates these symlinks inside the target project:

• ./.agents/skills/clawteam
• ./.claude/skills/clawteam

Run the same script again any time you want to refresh or recreate those links.

Typical Uses

• Run targeted local validation after code changes
• Reproduce a spawn / board / task / inbox / harness bug
• Smoke-test the real CLI in tmux or subprocess mode
• Review ClawTeam workflows end-to-end from the current repository checkout

Fast Validation

Prefer the smallest validation that proves the change.

ruff check clawteam/ tests/
pytest tests/<target_file>.py -q

Use broader runs only when the change crosses modules: