pre-submit-pr

Pre-submit validation automates checks before PR creation, running linting, tests, alignment reviews, and RFC analysis to catch issues early. This reduces manual review time by enforcing standards automatically on your feature branch.

Pre-submit PR validation covers lint and style enforcement, unit and integration tests, alignment with project guidelines, RFC compliance assessment, and PR metadata validation including branch status and commit history.

Yes, you can run pre-submit checks on your current branch before creating or updating a PR. This catches code quality issues, test failures, and compliance problems locally, preventing out-of-date or non-compliant submissions.

Pre-submit validation integrates into CI workflows as a gating step applicable across feature branches, running repository hooks and scripted checks to report blocking issues before PR submission, ensuring consistent code standards.

Pre-submit checks are automated, blocking validations that catch formatting, test, and compliance issues before review begins. Code review is manual and evaluates design, logic, and broader architectural concerns after these automated gates pass.

Pre-submit checks work with repository hooks and metadata parsing, so configuration depends on your repository structure. The Skill automates standard linting, testing, and alignment validation applicable to most codebases with CI setup.