review:pre-merge

Name: review:pre-merge
Availability: InStock
Author: jayteealao

Execute a senior-review-specialist agent to audit pull request changes.

Updated Dec 29, 2025

Search Tags:#automation #security #maintainability #code-review #git-diff #pre-merge #senior-review-specialist

Ready to run

npx skills add https://github.com/jayteealao/Aperture --skill review-pre-merge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review:pre-merge
Source: https://github.com/jayteealao/Aperture/tree/main/.claude/skills/review-pre-merge
Command: npx skills add https://github.com/jayteealao/Aperture --skill review-pre-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams ensure code changes meet quality, security, and maintainability standards by invoking a senior-review-specialist agent for comprehensive pre-merge analysis.

Core Features & Use Cases

Automated pre-merge assessment: Runs a senior-review-specialist to audit changes for correctness, tests, security, refactor safety, and maintainability.
Actionable reporter: Produces a structured pre-merge report with issues, severity, and remediation steps.
Use Case: A developer opens a PR; the Skill spawns the senior-review-specialist to generate a pre-merge checklist and suggested fixes.

Quick Start

Spawn the senior-review-specialist agent to begin the pre-merge review on the current working tree.

Frequently Asked Questions about review:pre-merge

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

FAQPage Schema

How do I automate pre-merge code review for pull requests?▼

Automating pre-merge code review involves analyzing git diff changes for correctness, security, and maintainability before merging. This skill orchestrates that assessment by applying structured checklists to each changed file and generating a report with remediation steps.

What is included in a thorough pre-merge code review checklist?▼

A thorough pre-merge checklist covers code correctness, test coverage verification, security vulnerabilities, refactor safety, and maintainability. It requires cross-referencing imports and analyzing working tree changes to produce actionable severity-rated issues.

How do you verify test coverage and security before merging a git branch?▼

Verifying test coverage and security before merging involves executing a senior-review specialist process on the git diff. It analyzes changed files against five checklists, cross-references imports, and outputs a structured pre-merge report with identified issues.

Can I use an automated senior review specialist for pull request refactor safety analysis?▼

Yes, an automated senior review specialist can be used for pull request refactor safety analysis. It evaluates working tree changes, applies maintainability and security checklists, and produces a final pre-merge report detailing refactor risks and remediation steps.

What is the best way to analyze working tree changes before merging code?▼

The best way to analyze working tree changes is loading them via git diff and applying a multi-point checklist for correctness, tests, and refactor safety. This identifies severity-rated issues and generates suggested fixes in a structured pre-merge report.

Does a pre-merge code review report include specific remediation steps for identified issues?▼

Yes, a pre-merge code review report includes specific remediation steps for identified issues. The generated report provides severity ratings and actionable suggestions to resolve security, maintainability, and correctness problems before the final merge.