skills.rest
latticeHQ
latticeHQOFFICIAL
Explore all skills by this author →
GitHub

pull-requests

Guide Pull Request creation, review, and governance workflows in the Lattice Workbench repository.

Updated Aug 27, 2026
Search Tags:#workflow#github#governance#code-review#ci#pull-requests#pr-lifecycle
One-click install
npx skills add https://github.com/latticeHQ/latticeWorkbench --skill pull-requests-latticehq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-requests
Source: https://github.com/latticeHQ/latticeWorkbench/tree/main/.lattice/skills/pull-requests
Command: npx skills add https://github.com/latticeHQ/latticeWorkbench --skill pull-requests-latticehq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guidelines to create, review, and govern Pull Requests in this repository to ensure consistency, quality, and auditable changes.

Core Features & Use Cases

  • Lifecycle Rules: define PR submission, review, and merge flows.
  • CI & Governance: enforce checks, automated validations, and Codex-assisted reviews.
  • Consistent PRs: standardize titles, bodies, and editing workflows across contributors.
  • Use Case: Maintainers and contributors collaborate on PRs with traceable decisions and fast, safe merges.

Quick Start

Prepare a feature branch, submit a PR, and follow the governance steps until CI passes and Codex review is complete.

Frequently Asked Questions about pull-requests

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

FAQPage Schema
How do I enforce consistent pull request naming and structured PR bodies in a GitHub repository?▼

To enforce consistent PR naming and structured bodies, this Skill standardizes titles and editing workflows across contributors, ensuring every pull request follows a uniform submission format for traceable decisions.

What is the standard pull request lifecycle for squash-merging into the main branch?▼

The standard pull request lifecycle requires preparing a feature branch, submitting the PR, and completing governance steps until CI passes and Codex review is complete before performing a squash-merge into main.

Can I use Codex-assisted review loops to govern code review and CI validation workflows?▼

Yes, you can use Codex-assisted review loops to govern code review and CI validation workflows, applying automated validations and structured escalation procedures to ensure safe, fast merges.

Does this PR governance workflow require any specific CI dependencies or external components?▼

No specific CI dependencies or external components are required. This Skill operates without dependencies to guide contributors through PR submission, review, and merge flows using built-in governance rules.

What's the best way to handle escalation procedures when CI validation fails during a pull request?▼

The best way to handle CI validation failures is to follow the defined escalation procedures within the PR governance workflow, addressing automated check failures before completing the Codex review loop and merging.

When should I not use a squash-merge workflow for governing pull requests?▼

You should not use a squash-merge workflow if your repository requires preserving individual commit history on the main branch, as this governance process specifically enforces squash-merging to maintain a clean, auditable changelog.

Related Skills

Explore More Software Engineering Skills→
tygwantygwan
1

quality-gate

Automate quality validation at pre-commit, pre-merge, pre-release, and post-release CI gates.

Community
Advanced
doravidandoravidan

ralph-merge

Merge RALPH worktree changes into the main branch with optional squash.

Community
Basic
sburlsburl
26

submit-pr

Run pre-checks, create a pull request, and initiate Codex review.

Community
Advanced
bifrost-proxybifrost-proxy
112

github-actions-pat

Analyze GitHub Actions CI runs and PR code reviews via GitHub API.

Community
Advanced