← LeaderboardThe Skill Leaderboard

create-pr

Alias for pr-writer. Use when users explicitly ask for "create-pr" or reference the legacy skill name. Redirects to the canonical PR writing workflow.

Published by sickn33 ↗sickn33/agentic-awesome-skills

Try your first task

create-pr

Start a fresh conversation. Replace the highlighted placeholders.

Use create-pr to prepare one draft PR title and description through canonical pr-writer, treating create-pr only as its legacy alias; for [authorized repository] and its already committed [branch/base], analyze the complete actual diff and commits, then return text only: a convention-formatted title and concise body covering factual what/why, alternatives, reviewer context, and only verified [issue or ticket references]. Require an available, authenticated GitHub CLI; verify the real default/base branch and freshness first. If the worktree is dirty, authority, authentication, actual diff/base, mandatory repository-policy conflict, safety boundary, or success criteria is unavailable, stop and ask rather than committing, rebasing, pushing, opening/editing a PR, or inventing validation results. Do not include

Required inputs

[authorized repository]
[branch/base]
[issue or ticket references]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: create-prdescription: Alias for pr-writer. Use when users explicitly ask for "create-pr" or reference the legacy skill name. Redirects to the canonical PR writing workflow.risk: criticalsource: communitydate_added: "2026-01-30"

Alias: create-pr

This skill name is kept for compatibility.

When to Use

The user explicitly asks for create-pr or refers to the legacy skill name.
You need to redirect pull request creation work to the canonical pr-writer workflow.
The task is specifically about writing or updating a pull request rather than general git operations.

Use the available pr-writer skill as the canonical workflow for creating and editing pull requests. If the client requires qualified skill names, use the qualifier for the plugin that supplied this skill rather than assuming an external namespace.

Confirm that pr-writer is actually installed; otherwise report the dependency missing. Repository-native maintainer and merge rules still apply.

If invoked via create-pr, run the same workflow and conventions documented in pr-writer.

Example

User request:

Create a pull request for the current branch, follow the repository template, and include the validation results.

Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.