github-pr-assistant

Generate GitHub Pull Request titles and descriptions following Conventional Commits.

1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/sltc-dev/core-foundry --skill github-pr-assistant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-assistant
Source: https://github.com/sltc-dev/core-foundry/tree/main/skills/coding/github-pr-assistant
Command: npx skills add https://github.com/sltc-dev/core-foundry --skill github-pr-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating high-quality GitHub Pull Requests by assisting with title generation, detailed descriptions, and code review checks, ensuring adherence to best practices.

Core Features & Use Cases

  • Conventional Commits: Automatically generates PR titles following the Conventional Commits specification.
  • Detailed Descriptions: Creates comprehensive PR descriptions including summary, change type, details, breaking changes, and testing information.
  • Code Review Assistance: Helps ensure PRs meet quality standards before submission.
  • Use Case: After pushing code changes for a new feature, use this Skill to generate a well-formatted PR title like feat(auth): implement two-factor authentication and a detailed description outlining the changes, testing, and potential impact.

Quick Start

Use the github-pr-assistant skill to generate a PR title and description for the recent code changes.

Frequently Asked Questions about github-pr-assistant

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

FAQPage Schema
How do I generate a GitHub Pull Request title following Conventional Commits standards?

To generate a Conventional Commits Pull Request title, this Skill analyzes your code changes and automatically categorizes modifications to create structured titles like `feat(auth): implement two-factor authentication`.

What should be included in a detailed GitHub PR description for code review?

A detailed GitHub PR description should include a summary, change type, modification details, breaking changes, and testing information, all of which this Skill generates by analyzing your code changes.

How do I identify breaking changes in my code before submitting a pull request?

To identify breaking changes before submitting a pull request, this Skill analyzes your code modifications and highlights potential impacts within the generated PR description to ensure repository consistency.

Can I automatically categorize code modifications for my GitHub pull requests?

Yes, you can automatically categorize code modifications for GitHub pull requests by using this Skill to analyze changes and map them to Conventional Commits types like feat, fix, or refactor.

What is the best way to format a pull request description to improve code review efficiency?

The best way to format a pull request description for code review efficiency is to use this Skill to generate comprehensive summaries, categorize changes, and suggest testing procedures.

Does this PR assistant suggest testing procedures for my code changes?

Yes, this PR assistant suggests testing procedures by analyzing your code changes and including recommended testing steps within the detailed pull request description output.