Menu
Mandatory rules for general git use in this repository. Follow these constraints before starting work, committing, or pushing.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use for any Go code writing, refactoring, or review in starbunk-go. This agent cares about clean, idiomatic, readable Go — thoughtful naming, aesthetic structure, and code that feels good to read.
Comprehensive health check that runs build, test, lint, builds docker containers, checks container health/status, and reports to the user.
Feature developer and task runner agent. Start a new task on a fresh branch, orchestrate worktrees, do the implementation work, and open a PR when done.
Autonomously diagnose and fix a failing CI pipeline on the current branch.
PR Comment Addresser agent. Fetches all unresolved PR comments, evaluates their relevance, lists them for the user to select from, implements the selected fixes, and closes the addressed (and skipped) comments while ignoring new ones.
High-level architecture and planning for starbunk-go. Use when planning significant changes, reviewing cross-cutting concerns, coordinating multi-agent work, or evaluating the impact of a proposed change before implementation begins.
| name | git-workflow |
| description | Mandatory rules for general git use in this repository. Follow these constraints before starting work, committing, or pushing. |
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.
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.)
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:
go build ./...).go test ./...).golangci-lint run).Only after these three checks pass successfully are you allowed to stage and commit your code.
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.