skills.rest
Shawn-Guo-CN
Shawn-Guo-CNCOMMUNITY
Explore all skills by this author →
GitHub

pr-conventions

Enforce pull request conventions by analyzing commit history and requiring a test plan.

Updated Feb 15, 2026
Search Tags:#git#testing#code review#pull request#branching#commit history
One-click install
npx skills add https://github.com/Shawn-Guo-CN/agentfoundry-plugin-marketplace --skill pr-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-conventions
Source: https://github.com/Shawn-Guo-CN/agentfoundry-plugin-marketplace/tree/main/plugins/pr-conventions/skills/pr-conventions
Command: npx skills add https://github.com/Shawn-Guo-CN/agentfoundry-plugin-marketplace --skill pr-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces best practices for pull requests, ensuring comprehensive commit analysis and clear test planning, leading to higher quality code and smoother reviews.

Core Features & Use Cases

  • Full Commit History Analysis: Guides users to analyze all commits in a branch, not just the latest one, for a complete understanding of changes.
  • Mandatory Test Plan: Requires a structured test plan in the PR description, ensuring thorough testing strategies are documented.
  • Branch Push Convention: Promotes the use of git push -u for new branches, improving tracking and management.
  • Use Case: When submitting a new feature branch for review, this skill ensures you've considered all changes, documented a robust test plan, and followed standard Git practices.

Quick Start

When creating a pull request, analyze the full commit history and include a detailed test plan.

Frequently Asked Questions about pr-conventions

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

FAQPage Schema
How do I write a pull request with a complete commit history analysis?▼

A mandatory test plan in a pull request is a structured section documenting your testing strategies. It ensures thorough testing is clearly communicated during code review preparation for higher quality software.

How do I push a new git branch with upstream tracking?▼

To push a new git branch with upstream tracking, use the `git push -u` command. This branch push convention improves branch tracking and management for remote repository workflows.

What is the best way to standardize pull requests for code review?▼

The best way to standardize pull requests for code review is to enforce conventions like full commit history analysis and a mandatory test plan. This standardization leads to smoother reviews and higher quality code.

Do I need to include a test plan for every pull request?▼

Yes, you need to include a structured test plan for every pull request to enforce conventions. Documenting a robust testing strategy in the PR description ensures thorough code review preparation.

Related Skills

Explore More Software Engineering Skills→
mathiasbourgoinmathiasbourgoin
2

git-conventions

Standardize git commit messages, branch names, and pull request descriptions.

Community
Intermediate
baphledbaphled
1

pre-merge

Execute a pre-merge validation checklist for Pull Requests.

Community
Intermediate
acta0724acta0724

verification-loop

Automates multi-phase code quality verification including builds, linting, and testing before pull request creation.

Community
Intermediate
RamblurrRamblurr

Finishing a Development Branch

Verifies tests, formatting, and linting before creating a Pull Request.

Community
Intermediate