Skip to content
Skills Library
Programming · Automation

pr

/pr

Create a pull request with full validation. Use when ready to submit work for review.

Licence
MIT
Last repository change
03.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 03.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Create a pull request with full validation. Use when ready to submit work for review.

Arguments

/pr [base-branch]
Original author description

Create a pull request with full validation. Use when ready to submit work for review.

How it works

  1. Steps
Original SKILL.md headings · 74 lines, 356 words
SKILL.md preview
---
name: pr
description: Create a pull request with full validation. Use when ready to submit work for review.
disable-model-invocation: true
argument-hint: "[base-branch]"
---

# Create Pull Request

Run full validation, then create a PR if clean.

## Steps

1. **Run pre-push validation**

```
/sdlc-core:validate --pre-push
```

2. **If validation fails**, report the issues and stop. Do NOT push or create PR.

3. **Re-verify any test counts cited in the PR body.**

   `--pre-push` runs the pytest suite only. If the draft PR body cites results
   from integration smokes, E2E suites, soak tests, container tests, or any
   other harness *outside* `local-validation.py`, re-run those exact suites
   in this session and update the counts in the body to match the fresh run.

   Example: a PR body saying "266 unit tests, 20/20 container smoke, 8/8
   sequential E2E, 18/18 fresh-user-flow" requires `pytest tests/ -q`,
   `bash tests/integration/workforce-smoke/run-containers.sh`,
   `bash tests/integration/workforce-smoke/run-e2e.sh`, and
   `bash tests/integration/workforce-smoke/run-fresh-user-flow.sh` to all
   run *this session* before the PR is opened.

   Session memory of test counts goes stale fast — fixtures grow, assertions
   drift, environments change. Only numbers you have just observed this
   session belong in the body. If a suite cannot run in this environment
   (missing binary, no Docker, etc.), *delete the number from the body* and
   say so explicitly rather than leaving a stale figure that cites another
   machine's result.

   If the PR already exists and counts have drifted post-creation, update
   the body in place rather than closing and recreating:
   ```bash
   gh pr edit <number> --body-file <updated-body.md>
   ```

4. **Verify required artifacts exist:**
   - Feature proposal in `docs/feature-proposals/`
   - Retrospective in `retrospectives/`
   - If either is missing, warn the user and ask whether to proceed.

5. **If validation passes**, proceed:
   - Check if the branch tracks a remote: `git branch -vv`
   - Push to remote with tracking: `git push -u origin <branch>`
   - Base branch defaults to `main` unless `$ARGUMENTS` specifies otherwise

6. **Create the PR** using `gh pr create`:

```bash
gh pr create --title "<short title under 70 chars>" --body "$(cat <<'EOF'
## Summary
<1-3 bullet points summarizing the changes>

## Changes
<List of files modified/created>

## Test plan
- [ ] `/sdlc-core:validate --pre-push` passes
- [ ] CI pipeline passes
<additional test steps as needed>

🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
```

7. **Report** the PR URL to the user.

Versions

RepositoryScoreLicence
This page · SteveGJones/ai-first-sdlc-practices100MIT
harlan-zw/harlan-claude-code100MIT
harlan-zw/harlan-agent-kit100MIT
jongio/skills100MIT
windmill-labs/windmill100Apache-2.0
opsmill/infrahub100Apache-2.0
nesquikm/dev-process-toolkit100MIT
tony/skills100MIT
tony/skills100MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 898f25fd3cde (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100kit-create-pr
    Commit changes and create a pull request with proper formatting. Use when ready to publish work for review.
  • 100create-pr
    Stage, commit, push, and open a pull request following project conventions and the Conventional Commits spec. Accepts an optional skip-checks argument to bypass validation when called from /build. Use when the user says "create a PR", "open a PR", "submit a pull request", or…
  • 100pr-create
    Use when work is complete and ready to create a PR for review. Triggers include "/pr-create", "create a PR", "commit and push", "open a PR".
  • 100create-pr
    Create high-quality pull requests via gh pr create. Use when the user wants to create a PR, submit a PR, open a pull request, submit for review, or push changes for review. Triggers on: create a pr, create-pr, submit a pr, open a pull request, submit for review, make a pr, gh pr create.
  • 100create-github-pr
    Create GitHub pull requests using the gh CLI. Use when the user wants to create a new PR, submit code for review, or open a pull request. Trigger keywords - create PR, pull request, new PR, submit for review, code review.
  • 100create-pr
    Create a pull request using the repository PR template. Use when asked to: create PR, open PR, push and create PR, submit PR, open pull request, send changes for review.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.