メニュー
Creates a GitHub pull request using the gh CLI. Use when the user asks to create, open, or submit a PR on GitHub.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generates pull request titles and descriptions. Use when the user asks to create, open, write, draft, or generate a PR, pull request, or merge request description.
Runs the local equivalent of the CI merge gate before you push. Detects which areas (Python, TypeScript, docs) your changes touch, auto-fixes what it can, then runs only those checks. Use when the user asks to run pre-push checks, get push-ready, verify changes before pushing or opening a PR, "make sure CI will pass", or check lint/tests/types locally.
Assess a published or in-progress documentation page for quality, accuracy, and voice compliance. Use before rewriting a page, during periodic health checks, when community signals point to confusion, or when comparing against competitor docs. Also triggers on "audit this page", "assess the docs", "what's wrong with this page", "check docs quality", "review this doc page".
Review documentation drafts for voice consistency, structure, and terminology before PR submission. Use after completing a draft, when checking if docs are ready to ship, or automatically after docs-writer produces output. Also triggers on "review this draft", "check my docs", "is this ready to ship", "review before merging".
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X", "document this feature".
Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.
| name | pr-create |
| description | Creates a GitHub pull request using the gh CLI. Use when the user asks to create, open, or submit a PR on GitHub. |
.local/pr-body.md. If it exists, re-read it fresh and sanity-check that its content matches the current branch's changes (e.g. the description references files, features, or issues consistent with the current diff). If it looks stale or unrelated to the current changes, warn the user and offer to regenerate it.pr-writer skill to generate the title and body.Check for CONTRIBUTING.md (at the repo root or in docs/) and .github/PULL_REQUEST_TEMPLATE.md. Scan them for any recommended steps before opening a PR — common examples:
npm run lint, cargo fmt)npm test, pytest)If you find any such steps, list them and ask the user which ones they'd like you to run. Run whichever the user approves. If any step fails, show the output and ask how to proceed before continuing.
If neither file exists or they contain no actionable pre-PR steps, skip this and move on.
To run the local equivalent of the CI merge gate before opening the PR (lint, format, type-check, tests for the areas the change touches), use the pre-push skill — bash .agents/skills/pre-push/run-checks.sh.
Check whether the current branch has an upstream tracking branch with all commits pushed. If not, push before creating the PR. If the push fails, show the error and stop.
Ensure the final PR body is written to .local/pr-body.md (create .local/ if needed), overwriting any earlier draft. Then create the PR:
gh pr create \
--title "<title>" \
--body-file .local/pr-body.md \
--draft
--draft. Only omit it if the user explicitly asks for a non-draft PR.--repo — let gh infer the upstream from the git remotes so the PR targets the correct upstream repository.gh is not authenticated or the command fails, show the error and stop.