← ClaudeAtlas

commitlisted

Default commit rules for any of Sarah's projects — branches, one-thing-per-commit, message shape. Use whenever about to commit. If the project has its own commit-workflow skill, follow that too; it wins on conflict.
schen22/claude-config · ★ 0 · Code & Development · score 72
Install: claude install-skill schen22/claude-config
# Commit ## Branches - Orchestrator (the session Sarah talks to) commits on the project's working branch. Never push; pushing is Sarah's call. - Helpers commit only on `lane/<name>` in their own worktree. Never touch the working branch, never merge, never push. - Integrate a lane: `git rebase <main> lane/<name>` then `git merge --ff-only lane/<name>`. - After the full gate passes on the working branch, clean up the lane in the same step: `git worktree remove <path>` and `git branch -d lane/<name>` (plus any `worktree-agent-*` branch). A leftover lane is easy to mistake for unfinished work. - `git log --oneline -5` before the first commit — never assume repo state. - `git remote -v` before any push advice. No remote → say so; never "push when happy". - Before any push: `git fetch`; if the remote branch moved, `ListAgents` (who else pushes here?), then merge it in. Never force-push a shared branch. - Before staging: `git status` and `ListAgents`. If a peer session is busy in the same working tree (files change under you), stop and ask Sarah: wait for it to commit, or move it to its own worktree. Never commit around its half-done edits. ## One commit does one thing - One commit per `PLAN.md` item (or one clearly named part of one). - A test ships in the same commit as the change it proves. - Shared docs (`PLAN.md`, `CLAUDE.md`, `README.md`, `docs/`) are orchestrator-only. Helpers list doc-worthy facts in their report instead. - Docs go in their own commit, af