quick-pr-review

A pre-PR checklist automates quality assurance by running staged-change inspection via git diff, executing tests, lint checks, security scans, and documentation validation before you create a pull request. This Skill applies across any project type and supports both MCP-enabled and manual workflows, catching issues early to reduce review cycles.

Yes, this Skill provides a language-agnostic workflow that works with any project. It detects and runs appropriate test commands (npm test, pytest, etc.), applies lint checks, searches for code markers like TODO and FIXME, and validates documentation—all without requiring project-specific configuration.

A pre-PR checklist covers code quality review of staged changes, test execution and coverage, linting, security scanning, documentation updates, and performance considerations. It enforces functional requirements through git diff inspection and marker searches, then provides a complete report before PR submission.

No. This Skill supports both MCP-enabled and MCP-free workflows, so you can run pre-PR checks with or without additional integrations. The manual mode covers code review, test execution, linting, security scanning, and documentation checks using standard project commands.

By automating quality assurance before PR submission—verifying tests pass, linting succeeds, documentation is updated, and security issues are flagged—the checklist ensures reviewers receive code that meets baseline quality standards, eliminating common rejection reasons and speeding up review cycles.

Before PR creation, inspect staged changes via git diff for code quality, run your project's test suite to verify functionality, execute lint checks, search for unresolved TODO/FIXME/XXX markers, perform basic security scans, and confirm documentation is current. This Skill automates all these steps.