git-workflowlisted

# Git & PR Workflow Read this file fully before taking any git or PR action. --- ## Branches Each issue gets its own git worktree, created by running `python3 scripts/start_issue.py XCE-123` from the main repo. The branch name is the Linear issue ID (e.g. `XCE-123`), branched from `dev`. Do not create branches manually. If no worktree exists yet, ask the user to run the start script first. --- ## Commits ### Format ```markdown Type - Short description of what changed and why Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> ``` ### Types | Type | When to use | | --- | --- | | `Feat` | New feature or behaviour | | `Fix` | Bug fix | | `Refactor` | Code change with no behaviour change | | `Docs` | Documentation or skill file changes | | `Chore` | Tooling, formatting, dependency updates | | `Test` | Adding or updating tests | ### Rules - **One concern per commit** — don't bundle unrelated changes - Stage specific files by name, never `git add .` or `git add -A` - Always pass the commit message via heredoc to preserve formatting: ```sh git commit -m "$(cat <<'EOF' Type - Description of change Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> EOF )" ``` --- ## Pull Requests ### GitHub Tool Reference | Operation | Tool | | --- | --- | | List PRs / find PR number | `gh pr list --head <branch>` (Bash) | | Read PR details | `gh pr view <number>` (Bash) | | Update PR description or title | `mcp__github__update_pull_request` | | Add a PR comment | `mcp