skills.rest
neilmovva
neilmovvaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pull-requests

Manage pull request lifecycle with validation, CI checks, and merging.

Updated Feb 24, 2026
Search Tags:#automation#workflow#code review#github#codex#pr#ci
One-click install
npx skills add https://github.com/neilmovva/mux --skill pull-requests-neilmovva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-requests
Source: https://github.com/neilmovva/mux/tree/main/.mux/skills/pull-requests
Command: npx skills add https://github.com/neilmovva/mux --skill pull-requests-neilmovva

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidelines and automated tools to ensure efficient, compliant, and high-quality Pull Request (PR) management within the repository.

Core Features & Use Cases

  • PR Lifecycle Management: Rules for branch naming, merging strategies (squash-merge to main), and handling existing PRs.
  • CI/CD & Validation: Guidance on local validation, using helper scripts (wait_pr_ready.sh, wait_pr_checks.sh, wait_pr_codex.sh) to monitor CI and Codex status.
  • Codex Review Workflow: Detailed steps for interacting with the Codex AI for reviews, resolving comments, and ensuring PR readiness.
  • PR Structure & Content: Standards for PR titles, bodies (Summary, Background, Implementation, Validation, Risks, Pains), and attribution footers.

Quick Start

Use the pull-requests skill to get guidance on creating and managing a new pull request.

Frequently Asked Questions about pull-requests

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

FAQPage Schema
How do I automate GitHub pull request validation and CI checks?▼

Automate GitHub pull request validation by using helper scripts to monitor CI status and Codex reviews. These scripts enforce PR readiness by ensuring passing CI checks and AI approval before merging.

What is the standard structure for a GitHub pull request body?▼

A standard GitHub pull request body should include sections for Summary, Background, Implementation, Validation, Risks, and Pains, along with proper attribution footers to maintain compliance.

How do I handle Codex AI code reviews and resolve comments on a PR?▼

Handle Codex AI code reviews by following a detailed workflow to interact with the AI, resolving all generated comments, and ensuring the PR passes Codex approval before merging.

Do I need the gh CLI installed to manage pull request workflows with scripts?▼

Yes, you need the gh CLI installed to manage pull request workflows. The Skill's helper scripts rely on gh to automate status monitoring, CI checks, and branch operations.

What is the best way to manage the pull request lifecycle from creation to merge?▼

The best way to manage the pull request lifecycle is enforcing branch naming rules, using squash-merge to main, and running local validation alongside automated scripts to monitor CI and Codex status.

Related Skills

Explore More Software Engineering Skills→
yellow-seedyellow-seed
2

sync-codex

Port Dockerfile RUN and ENV steps into portable shell scripts for Codex environments.

Community
Advanced
tkerseytkersey
66

join

Automate GitHub PR management with CI gates and squash-merge via gh CLI.

Community
Advanced
mvillmowmvillmow
18

quality-run-linters

Run configured linters including mojo-format, markdownlint, and pre-commit checks in check or fix mode.

Community
Intermediate
HomericIntelligenceHomericIntelligence
18

verify-pr-ready

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

Official
Intermediate