pr-workflow_skill

This skill assists you create and manage PRs with auto-generated descriptions, templates, and automated review requests.

TypeScript

4

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill constellos/claude-code --skill pr-workflow

SKILL.md4.1 KB

Overview

This skill provides end-to-end pull request lifecycle management with intelligent PR description generation, template selection by work type, and automated review requests. It turns commits and branch/issue context into clear PR bodies, and helps update metadata, request reviewers, and auto-merge when checks pass.

How this skill works

The skill inspects recent commits, branch names, and linked issue numbers to generate a contextual PR description using conventional commit grouping and prebuilt templates. It selects a template based on work type (feature, fix, chore, docs, refactor), renders variables into the template, and can call GitHub CLI commands to create, update, request reviews, and enable auto-merge. It also reads CODEOWNERS to determine reviewers and supports editing labels, milestones, and draft/ready states.

When to use it

Creating a PR with an auto-generated description from commits or an issue
Picking and applying a PR template based on work type (feature/fix/docs/etc.)
Requesting reviewers automatically from CODEOWNERS or manually
Updating PR metadata: labels, milestones, reviewers, or draft status
Enabling auto-merge once CI checks pass

Best practices

Use conventional commit messages (feat:, fix:, docs:, chore:, refactor:) so grouping is accurate
Include linked issue references using "Closes #N" to automate issue tracking
Choose the template that matches the work type to surface relevant sections (testing, root cause, summary)
Request CODEOWNERS reviewers for the changed paths and add ad-hoc reviewers for context
Enable auto-merge for small, well-tested PRs and include preview URLs in the description

Example use cases

Create a feature PR: group commits by type, render a feature template, add related issue and create the PR via gh
Open a bug-fix PR: generate description showing root cause and resolution with a testing checklist
Update an existing PR: add labels, change milestone, convert to/from draft, or add reviewers
Request reviews from CODEOWNERS automatically for files touched in the branch
Enable auto-merge (squash) so the PR merges when CI passes and delete the branch afterwards

FAQ

Yes. It extracts issue numbers from branch names and can include the issue in the generated PR body (e.g., "Closes #N").

How are reviewers chosen automatically?

It parses .github/CODEOWNERS for matching paths and uses those entries to add reviewers; you can also add reviewers manually.

Does it support different merge strategies?

Yes. It supports enabling auto-merge with strategies like squash and can delete the branch after merge.