agentweaver: Skill for Claude Code

Integration Workflow

dev is the default protected integration branch. Use a short-lived issue branch and a PR targeting dev; PRs are squash-merged so dev has one commit per logical change. main is stable/published-only and accepts only soaked release promotions or audited emergency hotfixes.

Issue branches use:

squad/{issue-number}-{kebab-case-slug}

Mandatory Worktree Isolation

Every locally run background agent making code changes MUST work in its own dedicated Git worktree. This is unconditional: it applies to issue-linked work and ad-hoc work alike. Never let a local agent make code changes from the shared primary checkout.

Use these naming conventions:

Work type	Branch	Worktree
Issue-linked	squad/{issue-number}-{short-kebab-slug}	.worktrees/{issue-number}-{short-kebab-slug}
Ad-hoc fix	fix/{short-kebab-slug}	.worktrees/{short-kebab-slug}
Ad-hoc maintenance/docs	chore/{short-kebab-slug} or docs/{short-kebab-slug}	.worktrees/{short-kebab-slug}

Coordinator responsibility

Whoever spawns a local background agent for any code change MUST put explicit worktree bootstrap commands (git fetch, git worktree add, and cd) in the spawn prompt. Do not assume the agent will infer this requirement or allow it to default to the shared primary checkout.

For an issue-linked task, the prompt must include commands equivalent to:

git fetch origin dev
git worktree add ".worktrees/{issue-number}-{slug}" \
  -b "squad/{issue-number}-{slug}" origin/dev
cd ".worktrees/{issue-number}-{slug}"

For an ad-hoc task, the prompt must include commands equivalent to:

git fetch origin dev
git worktree add ".worktrees/{short-kebab-slug}" \
  -b "fix/{short-kebab-slug}" origin/dev
cd ".worktrees/{short-kebab-slug}"

For example, two local agents that both run Git operations in the same directory can overwrite each other's checked-out branch or staged files, mixing uncommitted changes. Separate worktrees prevent that collision.