Two hard rules derived from reviewing real PRs:
- Rule 1: one PR = one atomic change (feature or bug fix that cannot
be further decomposed). Split multi-feat / multi-bug PRs before
submitting.
- Rule 2: every PR must include a verifiable validation method in the
description: officecli command sequence / shell or python script /
authoritative spec reference / screenshot. Bug fixes prefer command
sequences; features prefer screenshots.
Plus an explicit enforcement policy — either reject + ask for
resubmission (preferred, preserves the "Merged" badge) or cherry-pick
the valuable parts with a Co-authored-by trailer — so the maintainer
can handle non-compliant PRs without ad-hoc reconcile workflows.
English file is the canonical version; the Chinese file is a full
translation linked from the header of both files.
