skills.rest
jrmatherly
jrmatherlyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr-gates

Enforce preflight and gate-pr checks for pull requests with review evidence.

Updated Apr 14, 2026
Search Tags:#code review#pull request#migrations#verification#gates#preflight
One-click install
npx skills add https://github.com/jrmatherly/spacebot --skill pr-gates
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-gates
Source: https://github.com/jrmatherly/spacebot/tree/main/.claude/skills/pr-gates
Command: npx skills add https://github.com/jrmatherly/spacebot --skill pr-gates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a strict preflight and gate workflow for pull requests to prevent unsafe pushes, ensure migration safety, and require verifiable review closure so that changes land with evidence and minimal regressions.

Core Features & Use Cases

  • Preflight & Gate Enforcement: Require running just preflight and just gate-pr before finalizing changes or updating a PR.
  • Review Evidence Closure: For every P1/P2 review finding, capture file path and concise rationale, a targeted verification command, and pass/fail evidence.
  • Migration Safety: Prohibit edits to existing migrations and require new timestamped migrations for schema changes.
  • Handoff & Async Safety: Provide a standard handoff with summary, changed files, gate commands executed, mapping of findings to evidence, and residual risk; document state transitions, race windows, and idempotency when changing worker lifecycle or caches.

Quick Start

Prepare the PR by running just preflight, run just gate-pr before pushing, and include file references, verification commands, and evidence for any P1/P2 findings.

Frequently Asked Questions about pr-gates

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

FAQPage Schema
How do I enforce preflight checks before a pull request is merged?▼

Migration safety is enforced by prohibiting edits to existing migration files and requiring new timestamped migrations for schema changes, preventing partial or conflicting database state transitions.

How do I document evidence for code review findings on a pull request?▼

To document code review findings, capture the file path and concise rationale for every P1/P2 issue, provide a targeted verification command, and record pass or fail evidence to close the review loop.

What should a PR handoff include for asynchronous code review safety?▼

A PR handoff for async safety should include a summary of changes, affected files, gate commands executed, a mapping of review findings to evidence, residual risk notes, and documented state transitions or race windows.

How do I prevent unsafe database migrations from being pushed to a repository?▼

Migration safety is enforced by prohibiting edits to existing migration files and requiring new timestamped migrations for schema changes, preventing partial or conflicting database state transitions.

Related Skills

Explore More Software Engineering Skills→
RooseveltAdvisorsRooseveltAdvisors
1

just

Execute project-specific commands defined in a justfile using the just runner.

Community
Basic
yocxy2yocxy2

land-and-deploy

Merge pull requests and verify production deployment health with canary checks.

Community
Advanced
cescraflicescrafli

laravel-verification

Automates Laravel project verification including linting, static analysis, tests, security scans, and deployment readiness checks.

Community
Advanced
spallempatispallempati

branch-protection

Configure branch protection rules requiring pull request reviews before merging.

Community
Intermediate