skills.rest
remiboivin021
remiboivin021COMMUNITY
Explore all skills by this author →
GitHub

review

Review merge requests against approved scope and upstream gates.

Updated Feb 19, 2026
Search Tags:#commit#maintainability#merge#review#scope#gate
One-click install
npx skills add https://github.com/remiboivin021/synexis --skill review-remiboivin021
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/remiboivin021/synexis/tree/main/.agents/skills/review
Command: npx skills add https://github.com/remiboivin021/synexis --skill review-remiboivin021

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gate merges by enforcing scope discipline, verify upstream gates, and ensure maintainability before integration.

Core Features & Use Cases

  • Final merge authority to enforce branch integrity and long-term maintainability by validating upstream gates (QA/security/ADR) and required artifacts.
  • Detect hidden scope creep by comparing changes against approved scope and decision artifacts.
  • Verify commit atomicity and message quality, and provide concrete fixes or escalation when blockers exist.
  • Escalate to architects or ADRs when structural drift or unknown evidence is detected.

Quick Start

Reviewers invoke this skill during pull request reviews to confirm scope adherence and gate completion before merging.

Frequently Asked Questions about review

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

FAQPage Schema
How do I enforce scope discipline and prevent hidden scope creep during a pull request review?▼

Identify scope creep by comparing pull request changes against approved scope and decision artifacts. This merge review process evaluates commit atomicity and enforces branch integrity before allowing integration.

What is the best way to verify required upstream gates like QA, security, and ADRs before merging a branch?▼

Verify required upstream gates by checking for the presence of evidence artifacts like QA, security, and ADRs during the merge review. The process blocks integration and escalates if required evidence is missing or unknown.

How does merge review handle structural drift or missing evidence artifacts in a pull request?▼

Merge review handles structural drift by escalating to architects or ADRs when unknown evidence is detected. It outputs prioritized evidence and concrete corrective actions to resolve blockers before integration.

Can I use this to check commit atomicity and message quality before approving a merge?▼

Yes, you can check commit atomicity and message quality during merge reviews. The process evaluates commits against maintainability gates and outputs concrete fixes or escalations when blockers exist.

When should I escalate a pull request review instead of requesting changes directly?▼

You should escalate a pull request review when structural drift or unknown evidence artifacts are detected. Escalation routes the review to architects or ADRs rather than providing standard corrective actions.

Related Skills

Explore More Software Engineering Skills→
OpenCovenOpenCoven
20

pr-agent

Automate review, prepare, and merge phases of Pull Request workflows.

Official
Intermediate
tonehqtonehq
11

grill-me

Identify decision branches and map dependencies in a plan.

Official
Advanced
hairihouhairihou

git-conventions

Enforce Conventional Commits syntax for Git commit messages and branch naming.

Community
Basic
HomericIntelligenceHomericIntelligence
18

verify-pr-ready

Validate GitHub Pull Requests for CI status, approvals, and merge conflicts.

Official
Intermediate