version: "1.0.1"
An 800-line PR is likely too large to review effectively. Split it into smaller, independently understandable logical changes, keeping each PR preferably below 300 changed lines where practical. Separate refactors, formatting-only changes, behavior changes, tests, and documentation when they do not need to be reviewed together.
Before splitting, self-review the diff and identify dependencies. Create focused branches with the appropriate prefix, such as refactor/..., feat/..., or fix/...; order the pull requests if one depends on another. Each PR should explain what changed, why, how it was tested, and any issue link. Keep each commit focused and use Conventional Commit messages. Rebase a feature branch when needed to maintain a clean linear history, then ensure linting, tests, and builds pass before requesting merge.