Skip to content
Back to skills

Simple Pr

ASecurity

Create a simple PR from staged changes with an auto-generated commit message

  • 16,161 stars
  • 0 votes
  • 1 copy
  • 6 views
  • Added June 1, 2026
developmentgit

Security analysis

A100/100

Scanned June 1, 2026

npx -y skills add quickwit-oss/tantivy --skill simple-pr --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Simple Pr?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Simple Pr
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/quickwit-oss-simple-pr/badge)](https://www.skillsdirectory.com/skills/quickwit-oss-simple-pr)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: simple-pr
description: Create a simple PR from staged changes with an auto-generated commit message
disable-model-invocation: true
---

# Simple PR

Follow these steps to create a simple PR from staged changes:

## Step 1: Check workspace state

Run: `git status`

Verify that all changes have been staged (no unstaged changes). If there are unstaged changes, abort and ask the user to stage their changes first with `git add`.

Also verify that we are on the `main` branch. If not, abort and ask the user to switch to main first.

## Step 2: Ensure main is up to date

Run: `git pull origin main`

This ensures we're working from the latest code.

## Step 3: Review staged changes

Run: `git diff --cached`

Review the staged changes to understand what the PR will contain.

## Step 4: Generate commit message

Based on the staged changes, generate a concise commit message (1-2 sentences) that describes the "why" rather than the "what".

Display the proposed commit message to the user and ask for confirmation before proceeding.

## Step 5: Create a new branch

Get the git username: `git config user.name | tr ' ' '-' | tr '[:upper:]' '[:lower:]'`

Create a short, descriptive branch name based on the changes (e.g., `fix-typo-in-readme`, `add-retry-logic`, `update-deps`).

Create and checkout the branch: `git checkout -b {username}/{short-descriptive-name}`

## Step 6: Commit changes

Commit with the message from step 3:
```
git commit -m "{commit-message}"
```

## Step 7: Push and open a PR

Push the branch and open a PR:
```
git push -u origin {branch-name}
gh pr create --title "{commit-message-title}" --body "{longer-description-if-needed}"
```

Report the PR URL to the user when complete.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.