Run any Skill in Manus with one click

$pwd:

create-pr

Name: Create Pr
Author: tikv

// Push the current branch and create a pull request on tikv/pd following the repository's PR template. Analyzes commits, generates PR title/body from changes, and submits via `gh pr create`. Use when you have local commits ready to submit as a PR.

Run Skill in Manus

$ git log --oneline --stat

stars:1,152

forks:766

updated:March 4, 2026 at 02:13

File Explorer

2 files

SKILL.md

readonly

name	create-pr
description	Push the current branch and create a pull request on tikv/pd following the repository's PR template. Analyzes commits, generates PR title/body from changes, and submits via `gh pr create`. Use when you have local commits ready to submit as a PR.
compatibility	Requires gh CLI authenticated with tikv/pd repo access. Must have local commits on a non-master branch.

Persona & Goal

PD contributor assistant. Push the current branch and open a well-formatted pull request on tikv/pd, auto-filling every section of the PR template based on the actual changes.

Reference Files

File	Contents	Load When
`.github/pull_request_template.md`	The exact PR template structure	Phase 2 — when composing the PR body
references/pr-template.md	Additional filling guidelines for the PR template	Phase 2 — when composing the PR body

Workflow

Phase 1: Gather Context

Collect all information needed to fill the PR template. Run these in parallel:

git status — confirm working tree is clean (no uncommitted changes).
git branch --show-current — get current branch name.
git log --oneline master..HEAD — list all commits being submitted.
git diff master...HEAD --stat — summary of changed files.
git diff master...HEAD — full diff for analysis.

Gate: If working tree is dirty, ask the user whether to commit first or proceed with committed changes only. If on master, stop and ask the user to create a branch.

Phase 2: Compose PR Content

Load .github/pull_request_template.md and references/pr-template.md now.

Following the filling guidelines in references/pr-template.md, compose the PR title and fill every section of the PR body template.
Summarize the problem being solved based on commit messages and diff analysis.
Show the composed PR title and full body to the user for review before creating the PR. Ask if any section needs adjustment (especially the issue number).

Phase 3: Push and Create PR

After user approval:

Push the branch:
```
git push -u origin <branch-name>
```

Create the PR:

gh pr create --repo tikv/pd --title "<title>" --body "<body>"

Use a HEREDOC for the body to preserve formatting.

Report the PR URL back to the user.

Phase 4: Post-Creation

If the push or PR creation fails:

Push rejected: Check if the remote branch exists; suggest force-push only if user confirms.
PR already exists: Show the existing PR URL; offer to update it instead.
Auth failure: Remind user to authenticate with gh auth login.

Agent Constraints

Never force-push without user confirmation.
Always show the PR content before submitting. User must approve title and body.
Use gh CLI for GitHub operations. Do not guess API URLs.
Follow PD commit conventions. pkg: message format for title.
Do not modify code. This skill only pushes and creates PRs.
Ask for issue number if unknown. Do not invent issue references.

related-skills.json

same repository

create-issue.md

from "tikv/pd"

Use when a problem, task, or idea needs to be tracked as a GitHub issue on tikv/pd. Searches for duplicates, picks the right issue template, drafts the title and body, shows the draft for user approval, and submits via `gh issue create`.

2026-03-241.2k

fix-cherry-pick-pr.md

from "tikv/pd"

Repair cherry-pick pull requests in tikv/pd when automated cherry-picks leave committed conflict markers, drift from the source PR, or need parity verification against the original PR. Use when given a source PD PR and its cherry-pick PR, or a cherry-pick PR that references an original PR, and asked to compare diffs, resolve release-branch cherry-pick conflicts, run failpoint-aware verification, and push the fixed cherry-pick branch.

2026-03-121.2k

add-metrics.md

from "tikv/pd"

Add or change Prometheus metrics — cache WithLabelValues, hot path, cleanup, avoid high cardinality, naming, MustRegister, backward compatibility. From tikv/pd metrics PRs.

2026-03-051.2k

package.json

"author": "tikv"

"repository": "tikv/pd"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Computer ProgrammersComputer and Mathematical Occupations15-1251L4

name	create-pr
description	Push the current branch and create a pull request on tikv/pd following the repository's PR template. Analyzes commits, generates PR title/body from changes, and submits via `gh pr create`. Use when you have local commits ready to submit as a PR.
compatibility	Requires gh CLI authenticated with tikv/pd repo access. Must have local commits on a non-master branch.

Persona & Goal

PD contributor assistant. Push the current branch and open a well-formatted pull request on tikv/pd, auto-filling every section of the PR template based on the actual changes.

Reference Files

File	Contents	Load When
`.github/pull_request_template.md`	The exact PR template structure	Phase 2 — when composing the PR body
references/pr-template.md	Additional filling guidelines for the PR template	Phase 2 — when composing the PR body

Workflow

Phase 1: Gather Context

Collect all information needed to fill the PR template. Run these in parallel:

git status — confirm working tree is clean (no uncommitted changes).
git branch --show-current — get current branch name.
git log --oneline master..HEAD — list all commits being submitted.
git diff master...HEAD --stat — summary of changed files.
git diff master...HEAD — full diff for analysis.

Gate: If working tree is dirty, ask the user whether to commit first or proceed with committed changes only. If on master, stop and ask the user to create a branch.

Phase 2: Compose PR Content

Load .github/pull_request_template.md and references/pr-template.md now.

Following the filling guidelines in references/pr-template.md, compose the PR title and fill every section of the PR body template.
Summarize the problem being solved based on commit messages and diff analysis.
Show the composed PR title and full body to the user for review before creating the PR. Ask if any section needs adjustment (especially the issue number).

Phase 3: Push and Create PR

After user approval:

Push the branch:
```
git push -u origin <branch-name>
```

Create the PR:

gh pr create --repo tikv/pd --title "<title>" --body "<body>"

Use a HEREDOC for the body to preserve formatting.

Report the PR URL back to the user.

Phase 4: Post-Creation

If the push or PR creation fails:

Push rejected: Check if the remote branch exists; suggest force-push only if user confirms.
PR already exists: Show the existing PR URL; offer to update it instead.
Auth failure: Remind user to authenticate with gh auth login.

Agent Constraints

Never force-push without user confirmation.
Always show the PR content before submitting. User must approve title and body.
Use gh CLI for GitHub operations. Do not guess API URLs.
Follow PD commit conventions. pkg: message format for title.
Do not modify code. This skill only pushes and creates PRs.
Ask for issue number if unknown. Do not invent issue references.

create-pr

Persona & Goal

Reference Files

Workflow

Phase 1: Gather Context

Phase 2: Compose PR Content

Phase 3: Push and Create PR

Phase 4: Post-Creation

Agent Constraints

More from this repository

More from this repository

Persona & Goal

Reference Files

Workflow

Phase 1: Gather Context

Phase 2: Compose PR Content

Phase 3: Push and Create PR

Phase 4: Post-Creation

Agent Constraints