Run any Skill in Manus with one click

create-pull-request

Stars12

Forks1

UpdatedJune 19, 2026 at 11:51

Create a GitHub pull request — fills the repo's PR template, conventional-commit title, ticket refs. Draft mode via `--draft`.

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

helderberto

helderberto/agent-skills

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	create-pull-request
description	Create a GitHub pull request — fills the repo's PR template, conventional-commit title, ticket refs. Draft mode via `--draft`.
disable-model-invocation	true

Create Pull Request

Mode: $ARGUMENTS

If --draft is passed, create as draft PR.

Workflow

Run in parallel:
- git fetch origin && git remote show origin | grep 'HEAD branch' | cut -d' ' -f5 (get base branch)
- git rev-parse --abbrev-ref HEAD | grep -oE '[A-Z]+-[0-9]+' (extract ticket ID)
- Search for PR template in order: .github/pull_request_template.md, .github/PULL_REQUEST_TEMPLATE.md, .github/PULL_REQUEST_TEMPLATE/ (directory of templates), docs/pull_request_template.md, pull_request_template.md
Run in parallel:
- git diff HEAD
- git diff [base-branch]...HEAD --unified=0
If a PR template was found, read it in full — it becomes the canonical structure for the PR body. Do not paraphrase or skip sections.
Review ALL commits (not just latest)
Ask the user (use AskUserQuestion when available; otherwise ask directly). Ask all at once where possible:
- Effort (required): how long the task took in hours (planning, reading, testing, all included)
- Changes (required): general overview of what was done
- Testing (optional): testing done that isn't visible in the diff
- Tricky parts (optional): anything hard, requiring multiple attempts, or non-obvious
- If template found, also surface any template-specific fields that can't be inferred from the diff (e.g. "Does this include breaking changes?", "What type of change is this?")
Draft title and body:
- Title must match: /^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test)($.*$)?: .+$/
- If template found: use the template verbatim as the body base — fill every section/placeholder using diff + user answers; check applicable checkboxes; do NOT add sections not in the template; do NOT omit any template sections
- If no template: use Summary + Test plan
- Reference ticket ID in body if found (e.g. Resolves TICKET-123)
- Incorporate user's answers into description — don't just repeat the diff
In parallel:
- Create branch if needed
- Push with -u if needed
- Create PR with gh pr create using HEREDOC (add --draft if requested)

Rules

If a PR template exists, the body MUST be the filled template — not a summary that references it
Return PR URL when done
Use gh CLI only
NEVER force push to main/master
NEVER push without user confirmation if already on main/master
NEVER create PR with uncommitted changes — commit first

More from this repository

same repository

architecture-audit

helderberto/agent-skills

Explore a codebase to surface architectural friction and propose refactors toward deep modules (simple interface, large implementation) as GitHub issue RFCs. Use when the user asks to audit architecture, find structural friction, or identify refactor opportunities across a codebase. Don't use for single-module interface design (use /codebase-design) or code-level review of a diff (use /code-review).

2026-07-1712

e2e

helderberto/agent-skills

Write end-to-end tests for user flows using Cypress. Use when user asks to "write e2e tests", "/e2e", "add Cypress tests", or wants to test a user flow end-to-end. Don't use for unit tests, component tests, or projects using Playwright, Puppeteer, or other non-Cypress frameworks.

2026-07-1712

i18n

helderberto/agent-skills

Audit internationalization coverage and find hardcoded strings. Use when user asks to "check i18n", "/i18n", "find hardcoded strings", "check translations", or wants to verify translation coverage. Don't use for backend string extraction, non-frontend code, or projects without an i18n library.

2026-07-1712

safe-repo

helderberto/agent-skills

Check for sensitive data in repository. Use when user asks to "check for sensitive data", "/safe-repo", or wants to verify no company/credential data is in the repository. Use `--diff` mode to scope to staged + unstaged changes only (e.g., before commit). Don't use for general code review, adding .gitignore entries, or scanning non-git directories.

2026-07-1712

build

helderberto/agent-skills

Implement one phase of a plan — reads the plan, finds the next incomplete phase, implements it with feedback loops, marks checkboxes, offers a commit (one phase per invocation). Use after /plan when a plan exists at `.specs/plans/<slug>.md`, or when the user asks to build or implement the next phase. Don't use for ad-hoc changes with no plan (use /tdd) or to check progress (use /test).

2026-07-1712

codebase-design

helderberto/agent-skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

2026-07-1712

Create Pull Request

Mode: $ARGUMENTS

If --draft is passed, create as draft PR.

Workflow

Run in parallel:

git fetch origin && git remote show origin | grep 'HEAD branch' | cut -d' ' -f5 (get base branch)
git rev-parse --abbrev-ref HEAD | grep -oE '[A-Z]+-[0-9]+' (extract ticket ID)
Search for PR template in order: .github/pull_request_template.md, .github/PULL_REQUEST_TEMPLATE.md, .github/PULL_REQUEST_TEMPLATE/ (directory of templates), docs/pull_request_template.md, pull_request_template.md

Run in parallel:

git diff HEAD
git diff [base-branch]...HEAD --unified=0

If a PR template was found, read it in full — it becomes the canonical structure for the PR body. Do not paraphrase or skip sections.

Review ALL commits (not just latest)

Ask the user (use AskUserQuestion when available; otherwise ask directly). Ask all at once where possible:

Effort (required): how long the task took in hours (planning, reading, testing, all included)
Changes (required): general overview of what was done
Testing (optional): testing done that isn't visible in the diff
Tricky parts (optional): anything hard, requiring multiple attempts, or non-obvious
If template found, also surface any template-specific fields that can't be inferred from the diff (e.g. "Does this include breaking changes?", "What type of change is this?")

Draft title and body:

Title must match: /^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test)($.*$)?: .+$/
If template found: use the template verbatim as the body base — fill every section/placeholder using diff + user answers; check applicable checkboxes; do NOT add sections not in the template; do NOT omit any template sections
If no template: use Summary + Test plan
Reference ticket ID in body if found (e.g. Resolves TICKET-123)
Incorporate user's answers into description — don't just repeat the diff

In parallel:

Create branch if needed
Push with -u if needed
Create PR with gh pr create using HEREDOC (add --draft if requested)

Rules

If a PR template exists, the body MUST be the filled template — not a summary that references it

Return PR URL when done

Use gh CLI only

NEVER force push to main/master

NEVER push without user confirmation if already on main/master

NEVER create PR with uncommitted changes — commit first