Run any Skill in Manus with one click

open-pr

Stars5

Forks0

UpdatedFebruary 7, 2026 at 04:52

Create or update a pull request with a terse semantic title and appropriate description. Use when creating a PR, opening a pull request, updating PR description, or when a PR already exists and the description should be checked and updated.

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

hutchic

hutchic/.cursor

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	Create or update a pull request with a terse semantic title and appropriate description. Use when creating a PR, opening a pull request, updating PR description, or when a PR already exists and the description should be checked and updated.

Open PR Skill

Create a new PR with a terse semantic title and body matching the project template, or—if a PR already exists for the branch—check and update the PR description (and title if needed).

When to Use

Use when creating a new pull request after pushing a branch
Use when a PR already exists and the description (or title) may be outdated

Prerequisites

GitHub access: GitHub MCP configured and enabled, or GitHub CLI (gh) installed and authenticated (gh auth status).
Pushed branch: Branch must be pushed before creating or updating the PR.

PR Title

Same convention as commit messages: <type>(<scope>): <description>. Semantic, terse (under 50 chars), imperative. See CONTRIBUTING.md and AGENTS.md.

PR Body

Align with .github/pull_request_template.md: Description, Type of Change, Changes Made, Testing, Checklist, Related Issues. Fill from the branch's commits and diff.

Create Flow (No PR Yet)

Check for existing PR (MCP: e.g. list/read PRs by head branch; or gh pr view / gh pr list --head <branch>). If a PR exists, use Update flow instead.
Compose terse semantic title and body from commits/diff.
Create PR: use GitHub MCP create-pull-request when MCP is available; otherwise gh pr create --title "..." --body "..." (or --body-file).

Update Flow (PR Exists)

Get current PR (MCP: pull request read; or gh pr view for title and body).
Compare with what the body/title should be given current commits/diff.
If outdated: use GitHub MCP update-pull-request when MCP is available; otherwise gh pr edit --body "..." and optionally --title "...".

Only update when description or title is inaccurate or incomplete.

Tooling

Prefer GitHub MCP when it is configured, enabled, and has access: use MCP tools to create or update PRs (e.g. create pull request, update pull request, pull request read). This keeps the flow in the agent and avoids depending on a local gh auth.
Otherwise use GitHub CLI (gh): installed and authenticated (gh auth status). If gh is not available, instruct the user to install and authenticate.

Related Artifacts

More from this repository

same repository

solid

hutchic/.cursor

Use this skill when writing code, implementing features, refactoring, planning architecture, designing systems, reviewing code, or debugging. This skill transforms junior-level code into senior-engineer quality software through SOLID principles, TDD, clean code practices, and professional software design.

2026-03-105

rebase-conflict-resolution

hutchic/.cursor

Resolve git rebase conflicts: when to accept main's version vs branch, how to remove conflict markers, and how to avoid duplicate sections. Use when resolving conflicts during git rebase (e.g. rebase onto main) or when continuing a rebase after fixing conflicts.

2026-03-105

validate-new-api-routes

hutchic/.cursor

When adding new API or server routes: document manual validation, add an automated check (smoke or test) that hits the route, wire it into the suite, and run that verification before marking the task complete. Use when adding new Nuxt/API routes, server endpoints, or similar.

2026-03-105

land-the-plane

hutchic/.cursor

Finish and ship work: sync task systems (taskmaster/beads if in use), ensure quality gates pass, run deslop, then shipit. Use when wrapping up a branch—closing tasks, cleaning AI slop, and opening or updating a PR.

2026-03-105

stage-related-files

hutchic/.cursor

Group and stage related changes for git commit. Use when staging files for commit, grouping related changes, or deciding what to include in each commit. Implements how to group changes and when to split commits.

2026-02-115

terse-semantic-commits

hutchic/.cursor

Write semantic commit messages in Conventional Commits format. Use when committing, writing commit messages, or when a terse semantic commit is required. Covers format, types, scope, imperative mood, and length.

2026-02-075

name	open-pr
description	Create or update a pull request with a terse semantic title and appropriate description. Use when creating a PR, opening a pull request, updating PR description, or when a PR already exists and the description should be checked and updated.

Open PR Skill

Create a new PR with a terse semantic title and body matching the project template, or—if a PR already exists for the branch—check and update the PR description (and title if needed).

When to Use

Use when creating a new pull request after pushing a branch
Use when a PR already exists and the description (or title) may be outdated

Prerequisites

GitHub access: GitHub MCP configured and enabled, or GitHub CLI (gh) installed and authenticated (gh auth status).
Pushed branch: Branch must be pushed before creating or updating the PR.

PR Title

Same convention as commit messages: <type>(<scope>): <description>. Semantic, terse (under 50 chars), imperative. See CONTRIBUTING.md and AGENTS.md.

PR Body

Align with .github/pull_request_template.md: Description, Type of Change, Changes Made, Testing, Checklist, Related Issues. Fill from the branch's commits and diff.

Create Flow (No PR Yet)

Check for existing PR (MCP: e.g. list/read PRs by head branch; or gh pr view / gh pr list --head <branch>). If a PR exists, use Update flow instead.
Compose terse semantic title and body from commits/diff.
Create PR: use GitHub MCP create-pull-request when MCP is available; otherwise gh pr create --title "..." --body "..." (or --body-file).

Update Flow (PR Exists)

Get current PR (MCP: pull request read; or gh pr view for title and body).
Compare with what the body/title should be given current commits/diff.
If outdated: use GitHub MCP update-pull-request when MCP is available; otherwise gh pr edit --body "..." and optionally --title "...".

Only update when description or title is inaccurate or incomplete.

Tooling

Prefer GitHub MCP when it is configured, enabled, and has access: use MCP tools to create or update PRs (e.g. create pull request, update pull request, pull request read). This keeps the flow in the agent and avoids depending on a local gh auth.
Otherwise use GitHub CLI (gh): installed and authenticated (gh auth status). If gh is not available, instruct the user to install and authenticate.