skills.rest
mattg101
mattg101COMMUNITY
Explore all skills by this author →
GitHub

git-pr-prep

Stage relevant changes, verify acceptance criteria, and create a Pull Request with GitHub CLI.

1|Updated Jan 5, 2026
Search Tags:#automation#git#code review#pull request#staging#github cli
One-click install
npx skills add https://github.com/mattg101/SolidLink --skill git-pr-prep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-pr-prep
Source: https://github.com/mattg101/SolidLink/tree/main/docs/dev/.agent/skills/git-pr-prep
Command: npx skills add https://github.com/mattg101/SolidLink --skill git-pr-prep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of preparing a Pull Request, ensuring code quality, clarity, and adherence to project standards before submission for review.

Core Features & Use Cases

  • Automated Staging: Ensures only relevant files are staged for commit.
  • Rigor Checks: Verifies code against acceptance criteria, removing temporary comments.
  • PR Artifact Creation: Generates or updates PR documentation with clear instructions for testers.
  • GH CLI Integration: Creates the Pull Request using the GitHub CLI with descriptive titles and bodies.
  • Use Case: After completing a new feature, use this skill to automatically stage your code, check for console.log statements, create a pr_123.md file detailing verification steps, and then open a pull request against the main branch.

Quick Start

Use the git-pr-prep skill to prepare your pull request for review.

Frequently Asked Questions about git-pr-prep

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

FAQPage Schema
How do I automate pull request preparation and code review checks?▼

Automating pull request preparation involves staging relevant file changes, verifying code against acceptance criteria, and creating the PR via the GitHub CLI to ensure code quality before merging.

What is the process for creating a pull request with the GitHub CLI?▼

Creating a pull request with the GitHub CLI requires staging your completed code, generating descriptive titles and bodies, and executing the CLI command to open the request against your target branch.

How do I ensure only relevant files are staged for a git commit?▼

Ensuring only relevant files are staged for a git commit requires automated staging processes that selectively group completed features while excluding temporary debug statements like console logs.

Can I generate PR documentation and verification steps automatically?▼

Generating PR documentation automatically creates an artifact file detailing verification steps and clear instructions for testers, ensuring project-specific coding standards are communicated before review.

Does the automated PR workflow require adherence to project-specific documentation?▼

Yes, the automated PR workflow requires adherence to project-specific documentation and coding standards to properly verify acceptance criteria and maintain code quality before merging.

What is the best way to verify code against acceptance criteria before submitting a PR?▼

The best way to verify code against acceptance criteria is automating rigor checks that remove temporary comments, validate completed features, and generate clear PR instructions for reviewers.

Related Skills

Explore More Software Engineering Skills→
MakisuoMakisuo
1.6k

clickhousectl-local-dev

Install and configure a local ClickHouse environment with clickhousectl.

Community
Intermediate
yukieijiyukieiji

deploy-to-vercel

Automates app deployment to Vercel via CLI or push with optional sandboxing support.

Community
Advanced
zeronx798zeronx798

requesting-code-review

Scan staged git changes for security issues and quality regressions.

Community
Advanced
tyler-dot-earthtyler-dot-earth
1

staging-git-hunks

List and stage git hunks by ID without interactive input.

Community
Intermediate