name	pr
description	Create a GitHub Pull Request against the default base branch, summarizing all changes on the current branch.
argument-hint	[optional hint: e.g. PR title/wording or follow-up like 'draft', 'merge']

Create Pull Request

Create a GitHub PR against the default base branch with a clear summary of all changes.

Argument Hint

If the user passed an argument, treat it as guidance, not a literal title or body. It may contain:

Title/body hints — wording, scope, type, or focus to bias the drafted PR (e.g. fix flaky tests, scope: api, emphasize the perf win).
Flags — adjustments to the gh pr create invocation (e.g. draft → --draft, base develop → --base develop, reviewer alice → --reviewer alice).
Follow-up instructions — actions to perform after creating the PR (e.g. merge, auto-merge, open in browser).
Combinations of the above.

Apply title/body hints when drafting in Step 3. Apply flags and follow-ups in Step 4 and after.

If no argument is provided, follow the default flow.

Repository Context

Default base branch: !git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo main
Current branch: !git branch --show-current
Working tree status: !git status
Commits ahead of base: !git log $(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo main)..HEAD --format='%h %s'
Full diff vs base: !git diff $(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo main)...HEAD
Upstream tracking: !git rev-parse --abbrev-ref @{upstream} 2>/dev/null || echo none

Step 1: Validate State

Using the context above:

If current branch equals the base branch: stop and tell the user to create a feature branch first.
If there are uncommitted changes in the status: warn the user and ask whether to proceed without them or stop.
If there are no commits ahead of base: stop and tell the user there's nothing to PR.

Step 2: Identify Unrelated Changes

Read the full diff in the context. Identify any files that appear unrelated to the branch's purpose — e.g. lockfile-only changes from unrelated installs, accidental edits, or changes from a different task. If such files are detected, ask the user:

"These files appear unrelated to the PR — should they be included in the description?

path/to/file1

path/to/file2"

Only use the confirmed-relevant changes when drafting the PR below.

Step 3: Draft PR Title and Body

Title: Short conventional-commit-style title (under 70 chars). Use the dominant change type (feat:, fix:, chore:, etc.).

Body: Use this exact format:

## Summary
<2-5 bullet points describing the key changes>

## Test plan
<Bulleted checklist of how to verify these changes>

Step 4: Push and Create PR

If upstream tracking is none in the context, push with: git push -u origin HEAD
Otherwise, push with: git push
Create the PR: gh pr create --base <base> --title "<title>" --body "<body>" using a HEREDOC for the body

Step 5: Print Summary

Print a summary of the PR to the user:

The PR title
The PR body (Summary and Test plan sections)
A bulleted list of files included in the PR (from git diff --name-only <base>...HEAD)
The PR URL

Más de este repositorio

mismo repositorio

repo-logo

zirkelc/skills

Generate a logo and a social banner for a GitHub repository and optionally add them to the repo (logo into the README, banner as the repo's social preview). Use when the user wants a repo logo, README logo, repo banner, GitHub social preview, or repo card image.

2026-06-260

copy

zirkelc/skills

Copy your latest message, or a specific part of it, to the user's clipboard. Use when the user wants to "copy that", "copy to clipboard", or grab a quote/snippet/command/code block from your previous answer without selecting it manually in the terminal (which mangles indentation and line breaks).

2026-06-110

release-please

zirkelc/skills

Merge an open Release Please PR on GitHub to cut a release, then monitor the release workflow and report the published version. Use when the user wants to release, ship, or publish a repo whose releases are managed by release-please.

2026-06-110

handoff

zirkelc/skills

Hand off the current Claude Code session to a fresh agent. Writes a self-contained markdown handoff document capturing the task, context, errors, reproduction, code snippets, and next steps, so a new agent (often in a different repo) can continue the work. Use when the user wants to "hand off", "transfer", or "continue this in another project/session".

2026-06-070

sync-skills

zirkelc/skills

Symlink every skill in this repo into the global Claude skills directory (~/.claude/skills) so edits in the repo are live everywhere. Inspects existing global skills first, classifies each as new / already-linked / content-update / conflict, silently applies safe changes, and asks before replacing a skill that comes from a different location or source. Use when the user wants to "sync skills", "link skills globally", or "make my repo skills available everywhere".

2026-06-050

commit

zirkelc/skills

Create a git commit with an auto-generated conventional commit message summarizing the changes. Optionally push to remote.

2026-05-080

name	pr
description	Create a GitHub Pull Request against the default base branch, summarizing all changes on the current branch.
argument-hint	[optional hint: e.g. PR title/wording or follow-up like 'draft', 'merge']

Create Pull Request

Create a GitHub PR against the default base branch with a clear summary of all changes.

Argument Hint

If the user passed an argument, treat it as guidance, not a literal title or body. It may contain:

Title/body hints — wording, scope, type, or focus to bias the drafted PR (e.g. fix flaky tests, scope: api, emphasize the perf win).
Flags — adjustments to the gh pr create invocation (e.g. draft → --draft, base develop → --base develop, reviewer alice → --reviewer alice).
Follow-up instructions — actions to perform after creating the PR (e.g. merge, auto-merge, open in browser).
Combinations of the above.

Apply title/body hints when drafting in Step 3. Apply flags and follow-ups in Step 4 and after.

If no argument is provided, follow the default flow.

Repository Context

Default base branch: !git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo main
Current branch: !git branch --show-current
Working tree status: !git status
Commits ahead of base: !git log $(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo main)..HEAD --format='%h %s'
Full diff vs base: !git diff $(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo main)...HEAD
Upstream tracking: !git rev-parse --abbrev-ref @{upstream} 2>/dev/null || echo none

Step 1: Validate State

Using the context above:

If current branch equals the base branch: stop and tell the user to create a feature branch first.
If there are uncommitted changes in the status: warn the user and ask whether to proceed without them or stop.
If there are no commits ahead of base: stop and tell the user there's nothing to PR.

Step 2: Identify Unrelated Changes

"These files appear unrelated to the PR — should they be included in the description?

path/to/file1

path/to/file2"

Only use the confirmed-relevant changes when drafting the PR below.

Step 3: Draft PR Title and Body

Title: Short conventional-commit-style title (under 70 chars). Use the dominant change type (feat:, fix:, chore:, etc.).

Body: Use this exact format:

## Summary
<2-5 bullet points describing the key changes>

## Test plan
<Bulleted checklist of how to verify these changes>

Step 4: Push and Create PR

If upstream tracking is none in the context, push with: git push -u origin HEAD
Otherwise, push with: git push
Create the PR: gh pr create --base <base> --title "<title>" --body "<body>" using a HEREDOC for the body

Step 5: Print Summary

Print a summary of the PR to the user:

The PR title
The PR body (Summary and Test plan sections)
A bulleted list of files included in the PR (from git diff --name-only <base>...HEAD)
The PR URL