skills.rest
SteveGJones
SteveGJonesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr

Create pull requests after pre-push validation and test count verification.

41|6|Updated Jul 12, 2025
Search Tags:#git#validation#code-review#pre-push#pull-request#pr-automation
One-click install
npx skills add https://github.com/SteveGJones/ai-first-sdlc-practices --skill pr-stevegjones
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/SteveGJones/ai-first-sdlc-practices/tree/main/plugins/sdlc-core/skills/pr
Command: npx skills add https://github.com/SteveGJones/ai-first-sdlc-practices --skill pr-stevegjones

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines code collaboration by ensuring pull requests are created only after full validation, reducing back-and-forth and accelerating the review cycle.

Core Features & Use Cases

  • Enforces pre-push validation before PR creation using /sdlc-core:validate --pre-push.
  • Verifies test counts and results cited in the PR body, prompting re-runs when counts drift.
  • Returns the PR URL to the user and guarantees the PR is opened only after successful validation.

Quick Start

Run pre-push validation, then create a PR if clean.

Frequently Asked Questions about pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull request creation only after pre-push validation passes?▼

Pre-push validation runs checks like test counts and results before a pull request is created. This ensures code is fully verified locally, and the PR URL is returned only when all checks pass, preventing broken code from entering the review cycle.

Can I prevent opening a pull request if my test counts drift from expected results?▼

You can prevent opening a pull request when test counts drift by verifying test results cited in the PR body. The system prompts test re-runs if counts drift, ensuring the PR is opened only after successful validation and verified test results.

What is the best way to generate a pull request description with verified test results?▼

The best way to generate a pull request description with verified test results is to use a pre-push validation workflow. It enforces checks, verifies test counts, and generates the PR description only after tests pass, returning the PR URL.

Does Git-based PR automation work without manual code review checks before pushing?▼

Git-based PR automation can enforce pre-push validation automatically, eliminating manual code review checks before pushing. It validates test results and counts, then creates the PR only if checks pass, streamlining code collaboration and accelerating reviews.

Why does my automated pull request fail to open when validation checks fail?▼

Your automated pull request fails to open because the workflow enforces pre-push validation. It guarantees the PR is opened only after successful validation, ensuring that any failing checks or drifting test counts block the PR creation process.

Related Skills

Explore More Software Engineering Skills→
s205109s205109
2

cck-verify

Verify .NET solution builds, tests, formatting, and git status before commits.

Community
Intermediate
taloncjonestaloncjones

ship

Automate code review, testing, version bump, merge, and post-merge cleanup for pull requests.

Community
Advanced
joeylife94joeylife94

ship

Automate code deployment with branch detection, tests, version bump, and pull request creation.

Community
Advanced
caseymanoscaseymanos

git-hooks

Configure Husky Git hooks for pre-commit linting, pre-push testing, and commit message validation.

Community
Advanced