一键在 Manus 中运行任何 Skill

a-sk-pr

星标2

分支0

更新时间2026年7月12日 12:56

Open a GitHub pull request for the current branch, filling the project's PR template properly. Pushes the branch if needed, fills the template body from the actual changes, picks the correct base branch, and creates the PR (respecting the repo's permission posture). Say "a_sk_pr" or "pr" when ready to open a PR. Generic and project-agnostic — imported from an upstream framework and de-coupled from it.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

mahsanamin

mahsanamin/agentic-devkit

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

a_sk_pr — open a pull request

An on-demand skill to open a clean PR for the current branch. It delegates the title + body drafting to the a_sag_pr_writer agent and keeps the git/gh actions here. No task-flow / config-file coupling.

When to use

Your branch is ready for review and you want a well-formed PR.
Triggers: "pr", "create pr", "a_sk_pr", "open a pull request".

Flow

Confirm readiness. The branch has committed work, is not a protected branch, and builds/tests are green (or say what's outstanding). git status clean or intentionally so.
Determine the base branch. Default to the repo's default branch (main/master) unless the branch was cut from a story/integration branch — then target that. State the base you'll use.
Push the branch to origin (git push -u origin <branch>) if it isn't already, per the permission posture (see step 5).
Fill the template. Find the project's PR template (.github/PULL_REQUEST_TEMPLATE.md or .github/PULL_REQUEST_TEMPLATE/*). Invoke the a_sag_pr_writer agent with the diff + template + any ticket context; it returns the title and the filled body (it does not run git/gh). If there's no template, produce a concise Summary / Changes / Testing body.
Create the PR per the repo's permission posture:
- Default (ask): show the title + body + base, get approval, then gh pr create --base <base> --title … --body ….
- Autonomous (git push / gh pr create already in .claude/settings.json allow): narrate "Creating PR against : " and proceed, only when genuinely PR-ready. Don't ask redundantly.

Never force-push. Report the PR URL.

Done-when

A PR exists against the correct base with a complete, template-filled body and a clear title; the branch is pushed; force-push was never used. Report the PR URL.

同仓库更多 Skills

同仓库

a-r-l-pr-review

mahsanamin/agentic-devkit

Review one or more GitHub PRs in an isolated git worktree using parallel agents, without disturbing the working repo. Local routine: for each PR it creates a dedicated review worktree on a review-pr-<N> branch (never your own working branch), runs the project's PR-review skill, optionally auto-posts the comments that clear a high bar, then tears the review worktree down. Use when asked to review a PR, review my assigned PRs, do a worktree PR review, or when a scheduled "PR review" routine fires. Parameterized: pass repo (full local clone path for unattended runs), pr (a number, a list, or "mine" = all PRs assigned to me), and optionally the review skill, parallelism, cleanup, and post (auto = post the comments that clear a high bar without asking, THE DEFAULT; draft = review only, post nothing). Invoke as `run a_r_l_pr_review for repo=<path> pr=<number|mine>`. Triggers even without the exact name: "review PR 123 in a worktree", "review the PRs assigned to me", "do an isolated review of this PR".

2026-07-222

a-sk-l-review-pr

mahsanamin/agentic-devkit

Review a GitHub PR end-to-end from just its URL. Give it a PR link (or owner/repo#N); it finds the repo you ALREADY have cloned locally (via a cached lookup, then a scan of your cd_w workspace — never a duplicate clone), clones into cd_w only if you don't have it, spins up a git worktree checked out on the PR's real head branch updated to latest, then runs the project's own review skill (review-pr) if it has one or the global global-pr-reviewer otherwise, auto-posts the comments that clear a high bar as GitHub inline review comments, and tears the worktree + local branch down. This is a SKILL, not a routine (no _r); a routine may call it. Use when asked to "review this PR <url>", "review a PR from its link", "do a full review of <github pull url>", or given a bare GitHub PR URL to review. Parameterized: pr (URL / owner/repo#N / number), post (auto | draft), reviewer (auto | project | global).

2026-07-222

a-r-l-staging-qa-sweep

mahsanamin/agentic-devkit

Unattended QA routine that smoke-tests a web flow on STAGING and files ONLY confirmed, reproducible bugs to a Jira epic. Local routine: it reuses the signed-in browser session, drives a named flow skill end-to-end on desktop and mobile viewports, applies a strict settle-and-reproduce verification gate, dedupes against the epic's existing children, and files clean bug tickets. Use when asked to smoke-test / QA a staging flow, hunt for reproducible bugs in a booking or signup funnel, or when a scheduled "staging QA" routine fires. Parameterized: pass flow_skill, base_url, epic, and ticket_creator. Invoke as `run a_r_l_staging_qa_sweep with flow_skill=<skill> base_url=<staging host> epic=<KEY>`. Triggers even without the exact name: "QA the app flow on staging and file bugs", "smoke test the booking funnel", "find reproducible defects on staging".

2026-07-122

a-sk-commit

mahsanamin/agentic-devkit

Create a clean, human-readable git commit for the current changes. Groups the diff into a coherent commit, writes a clear message in the project's style, and commits (respecting the repo's permission posture). Say "a_sk_commit" or "commit" when ready to commit. Generic and project-agnostic — imported from an upstream framework and de-coupled from it.

2026-07-122

a-sk-sonarqube-coverage

mahsanamin/agentic-devkit

Drive test coverage on the current change up to the project's SonarQube (or CI) coverage gate. Finds the coverage command, measures coverage on the changed/new code, writes tests following the project's testing conventions for the uncovered lines, and re-runs until the gate passes. Say "a_sk_sonarqube_coverage", "raise coverage to the gate", or "get coverage green". Generic and project-agnostic — imported from an upstream framework and de-coupled from it.

2026-07-122

a-sk-message-writer

mahsanamin/agentic-devkit

Write professional work messages (Slack, email, escalations, status updates) from the standpoint of a VP of Engineering / VP R&D. Use when the user asks to draft, rewrite, sharpen, or "make this sound better" for a message to colleagues, managers, clients, or cross-team threads, especially under deadline pressure or conflict. Protects delivery teams, makes trade-offs visible, stays factual and non-defensive.

2026-07-082

name

a_sk_pr

description

a_sk_pr — open a pull request

When to use

Your branch is ready for review and you want a well-formed PR.
Triggers: "pr", "create pr", "a_sk_pr", "open a pull request".

Flow

Confirm readiness. The branch has committed work, is not a protected branch, and builds/tests are green (or say what's outstanding). git status clean or intentionally so.
Determine the base branch. Default to the repo's default branch (main/master) unless the branch was cut from a story/integration branch — then target that. State the base you'll use.
Push the branch to origin (git push -u origin <branch>) if it isn't already, per the permission posture (see step 5).
Fill the template. Find the project's PR template (.github/PULL_REQUEST_TEMPLATE.md or .github/PULL_REQUEST_TEMPLATE/*). Invoke the a_sag_pr_writer agent with the diff + template + any ticket context; it returns the title and the filled body (it does not run git/gh). If there's no template, produce a concise Summary / Changes / Testing body.
Create the PR per the repo's permission posture:
- Default (ask): show the title + body + base, get approval, then gh pr create --base <base> --title … --body ….
- Autonomous (git push / gh pr create already in .claude/settings.json allow): narrate "Creating PR against : " and proceed, only when genuinely PR-ready. Don't ask redundantly.

Never force-push. Report the PR URL.

Done-when

A PR exists against the correct base with a complete, template-filled body and a clear title; the branch is pushed; force-push was never used. Report the PR URL.