open-pr

Open GitHub pull requests after validation, self-review, and CI checks pass.

Updated Jul 18, 2025

Search Tags:#code review #pull request #git workflow #github #branch management #quality gates #ci polling

Ready to run

npx skills add https://github.com/dougborg/stocktrim-openapi-client --skill open-pr-dougborg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/dougborg/stocktrim-openapi-client/tree/main/.claude/skills/open-pr
Command: npx skills add https://github.com/dougborg/stocktrim-openapi-client --skill open-pr-dougborg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams safely take a completed feature branch from implementation through PR creation without skipping validation, self-review, CI, or review-comment handling.

Core Features & Use Cases

Validation-first PR creation: Discovers the repo verification command and requires all checks to pass before running gh pr create.
Mandatory self-review for the full diff: Reviews changes via base...HEAD and cached diffs to catch bugs, secrets, debug code, missing tests, and edge cases.
CI and review polling with correct GitHub semantics: Waits for CI and detects review activity using polling scripts, including correct inline review comment retrieval via the GitHub API.

Quick Start

Ask the AI to run open-pr to push your current implementation-done branch, open a pull request against main, wait for CI, and then address all review comments until ready.

Frequently Asked Questions about open-pr

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

FAQPage Schema

How do I open a GitHub pull request only after CI passes and self-review is complete?▼

To open a pull request with guardrails, the workflow discovers the repo verification command, performs a mandatory self-review of the full diff, and waits for CI green status before executing gh pr create.

What's the best way to automate pull request creation from a completed feature branch?▼

Automating pull request creation from a completed feature branch involves automatic base-branch selection, deterministic verification discovery, and strict safety rules like never using --no-verify to ensure clean PR creation via gh.

How does CI polling work when waiting for GitHub pull request validation?▼

CI polling works by using provided polling scripts to wait for CI green status and detect review activity. It retrieves inline review comments correctly via the GitHub API to monitor validation status incrementally.

Can I use gh to create a pull request while enforcing strict safety rules like never using --no-verify?▼

Yes, you can use gh to create a pull request while enforcing strict safety rules like never using --no-verify. The workflow requires deterministic execution of verification discovery and staged-file git practices to maintain safety guardrails.

How do I resolve inline review comments on a GitHub pull request automatically?▼

Resolving inline review comments involves polling for review activity using GitHub API semantics, retrieving inline comments correctly via the API, and executing delegated remediation actions to address feedback until the PR is ready.

Why does my pull request workflow require a self-review of the full diff before creation?▼

Your pull request workflow requires a self-review of the full diff via base...HEAD to catch bugs, secrets, debug code, missing tests, and edge cases. This mandatory review step ensures comprehensive validation before proceeding to CI polling and PR creation.