From claude-harness-forge
Label the current path in the session tree (BRD §4.5) so it can be retrieved later via /tree <label>.
How this command is triggered — by the user, by Claude, or both
Slash command
/claude-harness-forge:branch <label>The summary Claude sees in its command listing — used to decide when to auto-load this command
# /branch Labels the current active path. Use after `/fork` to make the new branch retrievable. ## Usage - `/branch <label>` — assign `<label>` to the current path's head turn. ## Conventions - Labels are short (1-3 words) and descriptive: `argon2-attempt`, `bcrypt-rejected`, `cleanup-pass`. - One label per branch (latest wins if you re-label). - Don't use spaces; use hyphens. See `commands/tree.md` and `skills/tree-sessions/SKILL.md`. ## Runtime `node scripts/tree-sessions.js branch <session_id> <label>`.
Labels the current active path. Use after /fork to make the new branch retrievable.
/branch <label> — assign <label> to the current path's head turn.argon2-attempt, bcrypt-rejected, cleanup-pass.See commands/tree.md and skills/tree-sessions/SKILL.md.
node scripts/tree-sessions.js branch <session_id> <label>.
npx claudepluginhub rlpatrao/claude_harness_forge/branchDisplays Claude Code usage costs broken down by git branch or PR. Specify optional [branch-name] or omit to view all branches.
/branchCreates a git branch in format <issue_class>-<issue_number>-<adw_id>-<concise-name> from spec file, checks out and pulls main, then creates/switches to new branch. Outputs branch name.
/branchExecutes git branch operations including create from issue ID, merge with validation, delete, switch, and status, enforcing rules from project git-workflow.md.
/branchCreates Git branch named {type}/{ISSUE-KEY}-{kebab-description} using Jira issue key, auto-generates description from issue summary, handles existing branches, and optionally transitions issue to In Progress.