Commit and Push

Overview

Commit in reviewable batches, push the feature branch, draft PR/MR copy with a Test plan.

Path: inspect → batch → commit → push → draft PR title + description. Does not replace test-design judgment (see test-design) or TDD rhythm (see superpowers:test-driven-development).

Core principle: one commit = one reviewable intent with a Conventional-Compliant, non-obscured message; one PR = one shippable story with a falsifiable Test plan.

Core rules on copy: commit/PR message format is a hard gate — Conventional Commits, type(scope): subject, type from the standard enum, scope from repo convention; language is flexible (中文 / English), following the user's own phrasing/register, not translated into an alien voice.

When to Use

• User says commit / push / "commit and push" / draft or open a PR/MR
• Working tree mixes concerns that should not land in one commit
• Need a PR Summary + Test plan checklist