skills.rest
ArthTech-AI
ArthTech-AIOFFICIAL
Explore all skills by this author →
GitHub

pr

Validate changes with QA checks, commit, push, and open a GitHub pull request.

Updated Aug 27, 2026
Search Tags:#git#linting#pull request#github#type checking#qa checks
One-click install
npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill pr-arthtech-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/ArthTech-AI/Marketplace-extensions/tree/main/tests/fixtures/claude-setups/poweruser/.claude/skills/pr
Command: npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill pr-arthtech-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of preparing a pull request by guiding the full sequence from validation to commit, push, and PR creation with QA discipline.

Core Features & Use Cases

  • QA-Gated Workflow: Ensures linting, testing, and type-checking are completed before changes are published.
  • Safe Git Operations: Helps stage only the intended files, create a clear commit message, and push the correct branch.
  • GitHub PR Creation: Opens a pull request with a summary and test plan so reviewers can evaluate the change quickly.
  • Use Case: Use this when you have finished a feature branch and need a polished PR that is ready for review without skipping quality checks.

Quick Start

Use the pr skill to validate my current branch, create a commit, push it to GitHub, and open a pull request with a concise summary and test plan.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I create a GitHub pull request after passing lint and type checking?▼

Creating a GitHub pull request after lint and type checking requires running QA validation gates first, then safely staging files, committing with a descriptive message, pushing the branch, and opening the PR via the gh CLI with an included summary and test plan.

What is a QA-gated pull request workflow?▼

A QA-gated pull request workflow is a software delivery sequence that enforces linting, testing, and type-checking validation checks before code changes are committed, pushed, and published for review on GitHub.

Do I need the GitHub CLI installed to automate pull request creation?▼

Yes, you need the GitHub CLI installed to automate pull request creation, as the workflow relies on gh-based PR creation to push the validated branch and open the pull request with a summary and test plan.

How do I ensure safe git staging before opening a pull request?▼

To ensure safe git staging before opening a pull request, the workflow guides you through staging only the intended files and applying commit hygiene, preventing unintended changes from reaching the remote branch.

What is the best way to include a test plan in a GitHub pull request?▼

The best way to include a test plan in a GitHub pull request is to use a workflow that opens the PR with a concise summary and test plan via the gh CLI after passing QA gates, ensuring reviewers can evaluate the change quickly.

Why do my pull requests fail QA checks before code review?▼

Pull requests fail QA checks before code review when linting, testing, or type-checking gates detect errors in the staged changes, preventing unvalidated code from being pushed and published to GitHub.

Related Skills

Explore More Software Engineering Skills→
LeroyAdonisLeroyAdonis

ship-it

Push the current branch to GitHub and open a pull request.

Community
Advanced
SantiagoisperSantiagoisper

land-and-deploy

Merge pull requests, deploy code changes, and verify production readiness.

Community
Advanced
cipherstashcipherstash
17

Commit Workflow

Run pre-commit checks and create atomic conventional commits.

Official
Intermediate
HaveAPointHaveAPoint

auto-commit

Automate Git commits, pushes, and pull request creation.

Community
Intermediate