Run any Skill in Manus with one click

creating-pr

Stars5

Forks1

UpdatedApril 24, 2026 at 18:50

Create a GitHub pull request with a markdown-formatted description. Use when opening a PR from this repository, and default the base branch to develop unless instructed otherwise.

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

schonarth

schonarth/pivot

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

File Explorer

2 files

SKILL.md

readonly

name	creating-pr
description	Create a GitHub pull request with a markdown-formatted description. Use when opening a PR from this repository, and default the base branch to develop unless instructed otherwise.
disable-model-invocation	true

Creating PR

Use this skill when opening a pull request for this repository.

Start Here

Confirm the current branch and the intended base branch.
Default the base branch to develop unless the user says otherwise.
Review the diff and gather the key changes, tests, and risks. Do not describe only the recent commit(s); describe the overall PR changes.
Ensure the description is well-formatted with appropriate headings and lists for readability
Do not mention any unrelated files or changes that are not part of the PR.

Workflow

Confirm the branch to publish and the base branch.
Inspect the diff and identify the main changes.
Draft the PR body in markdown using PR Description Template.
Make sure the PR description is properly formatted with headings and lists.
Create the PR against develop unless otherwise instructed.
Verify the created PR title, base branch, and body formatting.

Rules

Do not use plain text descriptions.
Do not target any branch other than develop unless the user explicitly says so.
Keep the description concise, accurate, and markdown formatted.
Do not include unrelated changes or files in the description.
- Notes like "There is an unrelated untracked ADR file in the worktree that is not part of this PR" should not be mentioned in the PR description.
Include tests run and any known limitations.

Gotchas

Codex usually creates PRs with malformed descriptions. Always use markdown and check the formatting.
Keep unrelated changes out of the PR description. They simply do not belong there. Do not mention anything left out.

Suggested Commands

git branch --show-current
git diff --stat develop...HEAD
git diff develop...HEAD
gh pr create --base develop --title "<title>" --body-file <file>

Output Shape

Use a markdown body with these sections:

Summary
Changes
Tests
Notes
Validation

More from this repository

same repository

setting-up-serena

schonarth/pivot

Installs and configures the Serena MCP server for Claude Code and Codex, including client MCP registration, the TypeScript LSP plugin, Claude Code hooks, and project onboarding. Use when the user asks to set up Serena, install Serena, configure Serena MCP, or enable symbolic code navigation. Trigger keywords: set up serena, install serena, configure serena, serena mcp, serena setup, symbolic tools, typescript lsp.

2026-04-245

milestone-lifecycle

schonarth/pivot

Covers the full lifecycle of a roadmap milestone — scaffolding folders and task files before implementation, agent execution rules during implementation, and UAT readiness at handoff. Use when creating a new milestone scaffold, starting work from a 00-milestone-coordination.md file, executing any milestone task file, or preparing a milestone for UAT.

2026-04-215

scaffolding-adr

schonarth/pivot

Create a short, well-formed ADR capturing the core architectural decision for an approved SPEC. Use when a SPEC is approved and needs its governing ADR extracted or written.

2026-04-215

scaffolding-spec

schonarth/pivot

Create a new SPEC file for a roadmap milestone following the SDD template. Use when a milestone has been accepted but no SPEC file exists yet.

2026-04-215

decision-locking

schonarth/pivot

Resolve open decisions in prerequisite documents before scaffolding or implementation. Use when dependency docs still contain unresolved questions that block progress.

2026-04-215

name	creating-pr
description	Create a GitHub pull request with a markdown-formatted description. Use when opening a PR from this repository, and default the base branch to develop unless instructed otherwise.
disable-model-invocation	true

Creating PR

Use this skill when opening a pull request for this repository.

Start Here

Confirm the current branch and the intended base branch.
Default the base branch to develop unless the user says otherwise.
Review the diff and gather the key changes, tests, and risks. Do not describe only the recent commit(s); describe the overall PR changes.
Ensure the description is well-formatted with appropriate headings and lists for readability
Do not mention any unrelated files or changes that are not part of the PR.

Workflow

Confirm the branch to publish and the base branch.
Inspect the diff and identify the main changes.
Draft the PR body in markdown using PR Description Template.
Make sure the PR description is properly formatted with headings and lists.
Create the PR against develop unless otherwise instructed.
Verify the created PR title, base branch, and body formatting.

Rules

Do not use plain text descriptions.
Do not target any branch other than develop unless the user explicitly says so.
Keep the description concise, accurate, and markdown formatted.
Do not include unrelated changes or files in the description.
- Notes like "There is an unrelated untracked ADR file in the worktree that is not part of this PR" should not be mentioned in the PR description.
Include tests run and any known limitations.

Gotchas

Codex usually creates PRs with malformed descriptions. Always use markdown and check the formatting.
Keep unrelated changes out of the PR description. They simply do not belong there. Do not mention anything left out.

Suggested Commands

git branch --show-current
git diff --stat develop...HEAD
git diff develop...HEAD
gh pr create --base develop --title "<title>" --body-file <file>

Output Shape

Use a markdown body with these sections:

Summary
Changes
Tests
Notes
Validation