open-pr

Run local tests, create a pull request, and coordinate review with CI checks.

9|2|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/harnessprotocol/harness-kit --skill open-pr-harnessprotocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/harnessprotocol/harness-kit/tree/main/plugins/open-pr/skills/open-pr
Command: npx skills add https://github.com/harnessprotocol/harness-kit --skill open-pr-harnessprotocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open-pr streamlines the end of development work by running tests, creating a well-structured pull request, conducting a code review that blocks on MUST FIX issues, and verifying CI status so you can move toward merge confidently.

Core Features & Use Cases

  • Runs local tests first to prevent sending broken changes for review.
  • Creates or reuses a PR with a filled description template (no empty placeholders).
  • Performs a code review via the review skill and enforces MUST FIX items before proceeding.
  • Checks CI and attempts quick fixes (lint/format/typos/import issues) when failures are likely to be straightforward.
  • Hands off to /merge-pr once everything is green, without merging itself.

What users typically do with it

Use it when you’re done with a feature, want to push for review, or finish every step in an implementation plan and need a reliable path to a PR that’s ready for merging.

Quick Start

Tell the AI to open your PR by running the open-pr skill with the command: /open-pr.

Frequently Asked Questions about open-pr

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

FAQPage Schema
How do I automate pull request creation with local test validation and CI checks?

Automating pull request creation involves running local tests first, creating a structured PR with a filled description, conducting a code review, and verifying CI status. The workflow stops if tests fail or CI breaks, ensuring only validated branches move toward merging.

Can I use GitHub CLI to coordinate code review and CI checks before merging?

Yes, coordinating code review and CI checks uses the GitHub CLI for PR inspection and creation. The process enforces stopping on failing tests or CI, blocks progress on MUST FIX review items, and attempts quick fixes for straightforward lint or formatting failures.

What's the best way to ensure a feature branch is ready for code review?

Ensuring a branch is ready for review requires running local tests to prevent sending broken changes, creating a PR with a filled description template, and blocking the workflow on any MUST FIX items identified during the review.

Does the PR preparation workflow merge the branch automatically after CI passes?

No, the PR preparation workflow does not merge the branch automatically. Once local tests, code review, and CI checks are green, it hands off to a separate merge step to finalize the pull request.

How does code review block MUST FIX issues in an automated PR workflow?

Code review blocks MUST FIX issues by halting the workflow when critical items are identified. The automated process performs a review and enforces that all MUST FIX items are resolved before proceeding to CI checks and handoff.

Do I need GitHub CLI installed to run automated PR preparation?

Yes, GitHub CLI is required for automated PR preparation. The workflow uses the gh CLI specifically for PR inspection and creation, enforcing stopping conditions on failing tests or CI before allowing progress toward merging.