Menü
Use a file-only git working branch for agent changes. Start from the current main branch contents without carrying prior branch history, create a fresh branch named from the agent or a uuid, then make the code update there.
Technical guide for creating a new TeamClaw agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new local coding agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Hire an Engineer in TeamClaw. Use this when an Architect or Manager needs to add implementation capacity, choose the right engineer role fit, check headcount, and then execute the hire through the standard TeamClaw agent creation flow.
Use the local deterministic infra layer in `tools/infra/` when setting up or extending harness, testbed, or local server environment workflows. Read the infra README first, then wire the setup into `Makefile` where appropriate.
Use the local agent workspace memory model. Store durable hot memory in the agent `memory/` folder, use `notes/` for daily records and task-local notes, and keep both folders updated as work progresses.
Review a pull request or contribution deeply, explain it tutorial-style for a maintainer, and produce a polished report artifact such as HTML or Markdown. Use when asked to analyze a PR, explain a contributor's design decisions, compare it with similar systems, or prepare a merge recommendation.
Generate the stable TeamClaw release changelog at releases/v{version}.md by reading commits, changesets, and merged PR context since the last stable tag.
| name | git-use |
| description | Use a file-only git working branch for agent changes. Start from the current main branch contents without carrying prior branch history, create a fresh branch named from the agent or a uuid, then make the code update there. |
Use this skill when an agent needs an isolated git branch for implementation work.
Create a fresh development branch from the current main branch files only.
The branch should contain the current main snapshot, but it should not carry prior feature-branch history into the new work branch.
Use one of:
Examples:
architect_architectengineer_alpha019d9d8e-branchmain or sync the local files to the current main snapshot you intend to branch from.main as the starting point for the new work.This skill is for a clean agent work branch built from the current main files, not for preserving old feature-branch commit history.
If you need a history-light branch, prefer a fresh branch/orphan-style workflow that starts from the current project files and then records the new work cleanly.
main file state