Run any Skill in Manus with one click

Get Started

open-pr

Stars103

Forks5

UpdatedJuly 17, 2026 at 13:09

Open a GitHub pull request for OpenFirma. Use whenever you are asked to open a PR.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Firma-AI

Firma-AI/openfirma

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	open-pr
description	Open a GitHub pull request for OpenFirma. Use whenever you are asked to open a PR.

Open PR

Use this workflow whenever you are asked to open a GitHub pull request for OpenFirma.

Workflow

Inspect the repository state and active VCS.
Inspect the revision stack that will be included in the PR.
Inspect bookmarks or branches and remotes.
If the working copy is dirty, the stack is mixed, or the target history is already under review, load and follow the commit-guidelines skill before continuing.
Read the PR template.
Push the review head to the correct remote.
Open a draft PR with gh.
Concurrently, using sub-agents:
1. Verify the final PR body, title, base, and head.
2. Load and follow the verify skill. If verification fails, provide the parent agent with a report so that it can address the issues.
3. Perform an adversarial PR review.
Present the adversarial review findings to the user. Do not address or dismiss any finding until the user has reviewed it and provided explicit direction.
Iterate on the outcomes of the previous steps according to the user's direction until verification succeeds, the findings have been addressed or dismissed, and any resulting changes have been pushed and passed the verification and metadata checks in step 8. The updated PR must also pass another adversarial review unless the changes since the previous review are purely mechanical and do not change behavior or meaning.
Monitor the CI run triggered by the previous push. It must succeed. If not, failures must be triaged and addressed.
Mark the PR as "ready to review".

For jj repositories, create or update a bookmark that points at the intended review tip before pushing it to the selected remote.

Verify after creation

After creating the PR, inspect it with gh pr view and confirm:

title matches repo style
base branch is correct
head branch or bookmark is correct
body follows the PR template
all intended commits are included

If the body does not match what you requested, fix it immediately instead of assuming the create or edit step worked.

Output

Report the PR URL.

More from this repository

same repository

review-rust-code

Firma-AI/openfirma

Review Rust changes for correctness, robustness, documentation quality, and test coverage.

2026-07-19103

rust-tests-guidelines

Firma-AI/openfirma

Guidelines for writing Rust tests in OpenFirma.

2026-07-19103

write-rust-tests

Firma-AI/openfirma

Write Rust tests for OpenFirma crates while avoiding redundant coverage.

2026-07-19103

adversarial-review

Firma-AI/openfirma

Review changes ahead of opening a new PR, modifying an existing one or on demand by the user.

2026-07-17103

edit-pr

Firma-AI/openfirma

Edit a pre-existing GitHub pull request for OpenFirma. Use whenever you are asked to make changes to commits, branches or bookmarks that would affect an open GitHub PR.

2026-07-17103

commit-guidelines

Firma-AI/openfirma

Dirty repo, uncommitted changes, commit, amend, split, changeset, PR history: inspect repository state and prepare atomic Git commits or jj changesets. Use whenever the worktree is already dirty or you are about to commit or rewrite history.

2026-06-21103

Open PR

Use this workflow whenever you are asked to open a GitHub pull request for OpenFirma.

Workflow

Inspect the repository state and active VCS.

Inspect the revision stack that will be included in the PR.

Inspect bookmarks or branches and remotes.

If the working copy is dirty, the stack is mixed, or the target history is already under review, load and follow the commit-guidelines skill before continuing.

Read the PR template.

Push the review head to the correct remote.

Open a draft PR with gh.

Concurrently, using sub-agents:

Verify the final PR body, title, base, and head.
Load and follow the verify skill. If verification fails, provide the parent agent with a report so that it can address the issues.
Perform an adversarial PR review.

Present the adversarial review findings to the user. Do not address or dismiss any finding until the user has reviewed it and provided explicit direction.

Iterate on the outcomes of the previous steps according to the user's direction until verification succeeds, the findings have been addressed or dismissed, and any resulting changes have been pushed and passed the verification and metadata checks in step 8. The updated PR must also pass another adversarial review unless the changes since the previous review are purely mechanical and do not change behavior or meaning.

Monitor the CI run triggered by the previous push. It must succeed. If not, failures must be triaged and addressed.

Mark the PR as "ready to review".

For jj repositories, create or update a bookmark that points at the intended review tip before pushing it to the selected remote.

Verify after creation

After creating the PR, inspect it with gh pr view and confirm:

title matches repo style

base branch is correct

head branch or bookmark is correct

body follows the PR template

all intended commits are included

If the body does not match what you requested, fix it immediately instead of assuming the create or edit step worked.

Output

Report the PR URL.