Skip to content
Back to skills

Work Pr

ASecurity

Create a complete and well-documented Pull Request. Use when the user wants to create a PR, submit their changes, or prepare a merge request.

  • 5 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added May 28, 2026
ai-agentsgobashrefactoringgitdocumentation

Works with

  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 28, 2026

npx -y skills add christopherlouet/claude-base --skill work-pr --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Work Pr?

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

Security grade badge for Work Pr
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/christopherlouet-work-pr/badge)](https://www.skillsdirectory.com/skills/christopherlouet-work-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: work-pr
description: Create a complete and well-documented Pull Request. Use when the user wants to create a PR, submit their changes, or prepare a merge request.
disable-model-invocation: true
---

# Create a Pull Request

## Objective

Create a complete, well-documented PR, ready for review.

## Instructions

### 1. Check the state

```bash
# State of changes
git status --short

# Differences with the target branch
git diff main...HEAD --stat

# Commit history
git log main...HEAD --oneline
```

### 2. Prepare the branch

```bash
# Make sure to be up to date
git fetch origin
git rebase origin/main  # or merge depending on convention

# Check the tests
npm test

# Check the lint
npm run lint
```

### 3. PR Template

```markdown
## Description

[Clear summary of what this PR does in 2-3 sentences]

## Type of change

- [ ] New feature (feat)
- [ ] Bug fix (fix)
- [ ] Refactoring (refactor)
- [ ] Documentation (docs)
- [ ] Other: [specify]

## Changes

### Additions
- [Added file/function]

### Modifications
- [Modified file/function]

### Removals
- [Removed file/function]

## How to test

1. [Test step 1]
2. [Test step 2]
3. Check that [expected result]

## Checklist

- [ ] Code self-reviewed
- [ ] Tests added/updated
- [ ] Documentation updated
- [ ] No forgotten console.log
- [ ] Lint passes
- [ ] Build passes

## Screenshots (if UI)

[Before/After if applicable]

## Related issues

Fixes #[number] (or Refs #[number])
```

### 4. Create the PR

```bash
# Push the branch
git push -u origin $(git branch --show-current)

# Create the PR with GitHub CLI
gh pr create \
  --title "type(scope): description" \
  --body "$(cat PR_BODY.md)" \
  --base main
```

## Best practices

| Do | Don't |
|-------|--------------|
| Descriptive title | "Fix bug" |
| Complete description | Empty PR |
| Small focused PRs | Giant PRs |
| Tests included | PR without tests |
| UI screenshots | Undocumented UI changes |

## Rules

- ONE PR = ONE topic
- Always include tests
- Respond to comments quickly
- Squash if history is noisy

Files in this skill

  • SKILL.md2.1 KB
  • examples/pr-example.md3 KB

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…