How do I install the Prepare Pr skill?

Run npx skillmds@latest add xakki/prepare-pr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Prepare Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Prepare Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Prepare Pr free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Prepare Pr?

Xakki (@xakki) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Prepare Pr by xakki — Agent Skill

Name: Prepare Pr
Author: Xakki

Prepare Pr

Prepare a branch for a pull request — sanity-check the diff, run the quality gate, and draft a PR description from the commits. Safe by default (draft-only, no auto-push, no auto-PR). Triggers — RU "подготовь PR", "собери PR", "оформи пулреквест"; EN "prepare a PR", "draft a pull request", "get this branch ready for review".

Xakki Updated Sep 21, 2026

File contents

prepare-pr

Gets the current branch ready for review. Default mode is draft-only: it prepares the description and stops — it does not push or open a PR unless the user asks. Stops on a red quality gate.

Git mechanics (commit format, no force-push, explicit-path staging, no trailers beyond Agent: <zone>) follow the git-flow core. This skill adds only the PR-assembly delta below.

Steps

Sanity. git status (clean? what's staged/untracked?) and git log <base>..HEAD + git diff <base>..HEAD to see what the PR contains.
Quality gate — delegate to qa-check. Do not re-implement the checks here. If qa-check is red → stop, report, fix root cause first.
Secret / artifact leak guard. Warn on suspicious untracked or staged files — never index them: .env, *.pem, id_rsa, *.session, *credentials*, dump.sql, *.bak. Add specific files (git add <path>), never git add . / -A.
Draft the PR description from the commits — sections: Задача / Task, Что сделано / What changed, Что проверять / How to verify, Артефакты / Artifacts (links, migrations, config). Keep it factual.
Stop (draft mode). Present the description + file list. Proceed to commit / push / open-PR only on explicit user request and per the mode chosen in ask-on-first-use.

Never (PR-specific)

Commit directly to the base branch (master/main) without an explicit request.
Push or open a PR automatically because the gate passed.

(General staging / force-push / no-verify / trailer rules → git-flow core.)

ask-on-first-use (per project)

Ask the user (don't guess) and offer to save to the project's .claude/:

Base branch (master / main / other).
Mode — draft (default), commit, push, or create-PR.
PR title convention + body template (any project-specific format).
(optional) Secret deny-list additions beyond the defaults above.

---name: prepare-prdescription: Prepare a branch for a pull request — sanity-check the diff, run the quality gate, and draft a PR description from the commits. Safe by default (draft-only, no auto-push, no auto-PR). Triggers — RU "подготовь PR", "собери PR", "оформи пулреквест"; EN "prepare a PR", "draft a pull request", "get this branch ready for review".---# prepare-prGets the current branch ready for review. **Default mode is draft-only**: itprepares the description and stops — it does **not** push or open a PR unless theuser asks. Stops on a red quality gate.Git mechanics (commit format, no force-push, explicit-path staging, no trailersbeyond `Agent: <zone>`) follow the [git-flow](../git-flow/SKILL.md) core. Thisskill adds only the PR-assembly delta below.## Steps1. **Sanity.** `git status` (clean? what's staged/untracked?) and `git log <base>..HEAD` + `git diff <base>..HEAD` to see what the PR contains.2. **Quality gate — delegate to [`qa-check`](../qa-check/SKILL.md).** Do not re-implement the checks here. If qa-check is red → **stop**, report, fix root cause first.3. **Secret / artifact leak guard.** Warn on suspicious untracked or staged files — never index them: `.env`, `*.pem`, `id_rsa`, `*.session`, `*credentials*`, `dump.sql`, `*.bak`. Add **specific files** (`git add <path>`), never `git add .` / `-A`.4. **Draft the PR description** from the commits — sections: **Задача / Task**, **Что сделано / What changed**, **Что проверять / How to verify**, **Артефакты / Artifacts** (links, migrations, config). Keep it factual.5. **Stop (draft mode).** Present the description + file list. Proceed to commit / push / open-PR **only on explicit user request** and per the mode chosen in ask-on-first-use.## Never (PR-specific)- Commit directly to the base branch (master/main) without an explicit request.- Push or open a PR automatically because the gate passed.(General staging / force-push / no-verify / trailer rules → git-flow core.)## ask-on-first-use (per project)Ask the user (don't guess) and offer to save to the project's `.claude/`:1. **Base branch** (`master` / `main` / other).2. **Mode** — `draft` (default), `commit`, `push`, or `create-PR`.3. **PR title convention + body template** (any project-specific format).4. *(optional)* **Secret deny-list** additions beyond the defaults above.

Frequently asked questions