Git

Never push directly to main/master:

• If current branch is main or master, create a new branch before committing/pushing
• Use a descriptive branch name based on the changes (e.g., fix/login-bug, feat/add-filter)
• Only push to feature/fix branches, never directly to the default branch

Always verify before acting:

• Check git status before staging
• Check git log for commit style
• Check remote tracking before push

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com

Use HEREDOC for multi-line messages:
```bash
git commit -m "$(cat <<'EOF'
Message here

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"

Test plan

• Test item 1
• Test item 2

🤖 Generated with Claude Code

</pr_format>

</essential_principles>

<intake>
What would you like to do?

1. **Commit** - Stage and commit changes
2. **Push** - Push commits to remote
3. **PR** - Open a pull request
4. **Ship** - Full workflow: commit + push + PR

**Wait for response before proceeding.**
</intake>

<routing>
| Response | Workflow |
|----------|----------|
| 1, "commit", "stage" | `workflows/commit.md` |
| 2, "push", "upload" | `workflows/push.md` |
| 3, "pr", "pull request", "open pr" | `workflows/pr.md` |
| 4, "ship", "full", "all" | Run commit → push → pr sequentially |

**After reading the workflow, follow it exactly.**
</routing>

<workflows_index>
| Workflow | Purpose |
|----------|---------|
| commit.md | Stage changes and create commit with proper message |
| push.md | Push commits to remote, create branch if needed |
| pr.md | Create pull request with gh CLI |
</workflows_index>