final-review

Name: final-review
Availability: InStock
Author: Glide

Validate code changes against tests, types, lint, and PR metadata before merging.

Updated Jan 16, 2026

Search Tags:#lint #code-review #CI #tests #type-check #pre-merge #PR-metadata

Ready to run

npx skills add https://github.com/glideapps/roto-rooter --skill final-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: final-review
Source: https://github.com/glideapps/roto-rooter/tree/main/.claude/skills/final-review
Command: npx skills add https://github.com/glideapps/roto-rooter --skill final-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the final pre-merge validation by auditing code changes for test coverage, type correctness, lint status, and PR metadata to prevent regressions.

Core Features & Use Cases

Comprehensive pre-merge validation: verifies tests cover changed files, types pass, lint issues are resolved, and PR metadata is up to date.
Change impact verification: ensures that changes are ready for merge by cross-checking affected modules and associated checks.
Use Case: Before opening a PR, run this Skill to confirm all checks pass and no critical issues remain.

Quick Start

Run the final-review command in your project to perform a pre-merge validation against main and your feature branch.

Frequently Asked Questions about final-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate pre-merge validation for tests, types, and lint status before opening a PR?▼

Pre-merge validation automates auditing code changes against test coverage, type correctness, lint rules, and PR metadata. You can run the final-review command in your project to cross-check affected modules and confirm all checks pass before merging.

What does a comprehensive pre-merge code review check to prevent post-merge regressions?▼

A comprehensive pre-merge code review verifies that tests cover changed files, type checks pass, and lint issues are resolved. It also validates PR metadata to ensure changes are fully ready for merge and to reduce post-merge issues.

Can I run pre-merge checks locally or does it require a CI pipeline integration?▼

Pre-merge checks support integration in both local development environments and CI pipelines. The validation requires access to git history, test runners, type checkers, and lint tools to successfully audit feature branches against the main branch.

What's the best way to verify feature branch readiness against main before merging?▼

To verify feature branch readiness, run a final pre-merge review command to cross-check affected modules and associated checks. This ensures changes are validated against tests, types, lint, and PR metadata to prevent regressions before opening a PR.

Do I need specific test runners and type checkers installed to validate PR readiness?▼

Yes, validating PR readiness requires access to git history, test runners, type checkers, and lint tools. These dependencies are necessary to automate the comprehensive pre-merge review and confirm that no critical issues remain.

Why should I use automated pre-merge validation instead of manually checking changed files?▼

Automated pre-merge validation streamlines auditing code changes by cross-checking affected modules and associated checks comprehensively. It confirms test coverage, type correctness, and lint status automatically, reducing post-merge issues caused by manual oversight.