What does the create-pr skill do?

create-pr is a compatibility alias that redirects pull-request creation work to the canonical pr-writer skill, maintaining the same workflow, inputs, outputs, and PR-writing conventions.

When should I use create-pr instead of pr-writer?

Use create-pr when a user explicitly asks for it by its legacy name or when a task specifically needs to redirect to the canonical pull-request workflow; for new invocations, use pr-writer directly instead.

Does create-pr implement pull-request creation itself?

No, create-pr does not implement pull-request creation itself; it only redirects the work to the pr-writer skill.

Skill

Create and Update Pull Requests

Name: Alias: create-pr
Availability: OnlineOnly
Author: Antigravity

A compatibility alias that redirects pull-request creation work to the canonical pr-writer skill.

Get skill

Antigravity

Own this? Claim it

Spark score

out of 100

Updated 20 days ago

Source checked Aug 31, 2026

Version 16.5.0

Add to Favorites

Why it matters

Automate the creation and updating of pull requests for code changes. This skill streamlines the process of submitting code for review and integration.

Outcomes

What it gets done

Initiate new pull requests based on code changes.

Update existing pull requests with further modifications.

Facilitate code review by preparing pull requests.

Redirect pull request tasks to the canonical 'sentry-skills:pr-writer' workflow.

Install

Add it to your toolbox

Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-create-pr | bash

After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.

Reports

Agent outcome reports

No reports yet

Overview

Alias: create-pr

A compatibility alias that redirects legacy create-pr invocations to the canonical pr-writer pull-request workflow. Use it when a user explicitly asks for create-pr by its legacy name; otherwise use pr-writer directly.

What it does

create-pr is a compatibility alias kept for backward compatibility with its legacy name. It does not implement pull-request creation itself; instead it redirects the work to the canonical pr-writer skill, running the same workflow and conventions documented there, including its inputs, outputs, and PR-writing conventions unchanged.

When to use - and when NOT to

Use it when a user explicitly asks for create-pr by its legacy name, or when a task specifically needs to redirect pull-request creation or editing to the canonical workflow rather than handling general git operations. If a client requires qualified skill names, qualify with the plugin that supplied this skill rather than assuming an external namespace. For any new invocation not tied to the legacy name, use pr-writer directly instead of this alias.

Who it's for

Users and tooling still referencing the legacy create-pr name who need it to transparently behave as pr-writer for pull-request creation and editing.

FAQ

Common questions

Discussion