| name | git-workflow |
| description | Mandatory rules for general git use in this repository. Follow these constraints before starting work, committing, or pushing. |
General Git Workflow
These are the strict rules for all Git usage in this repository. You MUST adhere to this workflow whenever tasked with writing code, fixing a bug, or implementing a feature.
1. Branching & Worktree Isolation
Always sync main first: Before starting any task, you must fetch and pull the latest changes from main to avoid drift.
git checkout main
git pull origin main
Always branch out: Never work directly on main. Create a descriptive branch (e.g., feat/..., fix/..., chore/...).
git checkout -b <branch-name>
Always use worktrees: You must isolate your work by adding a git worktree. This prevents state conflicts and keeps your workspace clean.
mkdir -p "$(dirname ".gemini/worktrees/<branch-name>")"
git worktree add .gemini/worktrees/<branch-name> <branch-name>
(Note: All subsequent code modifications must be performed inside this worktree directory.)
2. Pre-Commit Validation
Before you are allowed to execute a git commit, you MUST verify that your changes are sound locally. Run the following checks from within your worktree:
- Build: Ensure the code compiles successfully (
go build ./...).
- Test: Ensure all existing tests pass (
go test ./...).
- Lint: Ensure the linter is clean (
golangci-lint run).
Only after these three checks pass successfully are you allowed to stage and commit your code.
3. Pushing Rules
NEVER git push without express permission.
Even if your tests pass and you have successfully committed your changes to your isolated branch, you must STOP and ask the user for explicit permission before attempting to push your code or open a PR.
