egeetas Pull Request Preparation
Preparation does not authorize staging, committing, pushing, or opening a pull request; each action requires explicit authorization.
Prepare
- Resolve the intended base, head, issue/context, and acceptance criteria.
- Inspect the complete diff and working tree; exclude unrelated or accidental files.
- Self-review correctness, security, compatibility, data/config changes, generated files, tests, and documentation.
- Run relevant formatter, static checks, tests, and build. Record exact commands and results.
- Prepare a concise title and body covering why, what, verification, risk, migrations/config, rollout/rollback, and follow-ups.
- Add visual evidence only for material UI outcomes and remove sensitive data.
- Identify reviewer expertise and unresolved decisions without assigning reviewers unless authorized.
Keep the PR focused. Split independent changes when doing so improves review or rollback rather than merely reducing line count.