Branch and commit conventions that keep an agent's work reviewable — one branch per task, main stays clean, nothing force-pushed.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
All work happens on branches. Main stays clean. The user reviews before merge.
feat/TASK-ID-short-description # New features
fix/TASK-ID-short-description # Bug fixes
docs/TASK-ID-short-description # Documentation
research/TASK-ID-description # Exploration
refactor/TASK-ID-description # Code improvements
Examples:
feat/API-142-rate-limitingfix/WEB-87-login-redirectdocs/API-150-auth-guideTASK-ID: Brief description of change
- Detail 1
- Detail 2
Co-Authored-By: Claude <co-author>
Good commits:
git checkout main
git pull origin main
git checkout -b feat/TASK-ID-description
# Commit often
git add -A
git commit -m "TASK-ID: Implement X"
# Push periodically
git push -u origin feat/TASK-ID-description
# Ensure tests pass
cargo test # or npm test, pytest, etc.
# Push final state
git push
# Log completion (megg or BACKLOG.md)
git push --force).megg/blocked.md or commit messageThe user reviews branches by:
# See all work
git branch -a
# Review specific branch
git log main..feat/BRANCH-NAME
git diff main..feat/BRANCH-NAME
# Merge if good
git checkout main
git merge feat/BRANCH-NAME
For OpenSpec changes:
feat/add-plugin-systemFor critical bugs in production:
hotfix/description branchNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Look up how Claude Code itself works — hooks, skills, subagents, MCP, plugins, settings — from the official docs, so answers come from the current spec instead of memory.
The English summary is being prepared. Showing the original description.
Design better agents, skills and hooks for Claude Code, checking the current spec instead of guessing at fields.
The English summary is being prepared. Showing the original description.
Run a feature end to end — scout the code, plan it, build it, and keep a session file so a closed terminal doesn't lose the thread.
The English summary is being prepared. Showing the original description.
Close out a session — summarise what changed, capture what was learned, and prepare the commit.
The English summary is being prepared. Showing the original description.
Hand over a spec and walk away — plans, builds, tests and audits on its own, stopping only at a real blocker.
The English summary is being prepared. Showing the original description.
Run the project's own tests, linter, type checker and build, and report what actually failed.
The English summary is being prepared. Showing the original description.