commitlisted

# Commit Workflow > **Browser access.** Use the built-in browser tools. `mcp__Claude_Browser__*` > covers navigation, DOM reads (`read_page`), screenshots and `resize_window`; > reach for chrome-devtools `emulate` when a mobile *device* gate has to fire, > which `resize_window` alone does not guarantee. The `browser` skill and the > `agent-browser` steps were dropped in 8.79.0 — do not reach for that CLI here. > (The binary itself is still installed for kb-factory's JS-rendered crawls; > that is a separate consumer, not a fallback for page verification.) ## Working Tree !`git status --short 2>/dev/null` !`git diff --stat HEAD 2>/dev/null | tail -5` !`git log --oneline -5 2>/dev/null` ## Quick Commit ```bash # 1. Check what changed git status --short git diff --stat # 2. Stage specific files (prefer targeted adds over git add -A) git add src/components/new-feature.tsx src/lib/utils.ts # 3. Commit with conventional format git commit -m "feat: add playlist drag-drop reorder" ``` ## Evidence goes IN the commit If the change fixes a defect or moves a visible surface, the `prove` skill's before/after pair belongs in this commit, not beside it. Two reasons, and the second is the one that bites: - A reviewer reading the commit later has no other route to it. - `.claude/evidence/` is tracked, so evidence left uncommitted dirties the tree and any gate refusing a dirty tree then refuses to run at all. Name the paths in the body and state the delta in one line. A difference y