skills.rest
SeventeenthEarth
SeventeenthEarthCOMMUNITY
Explore all skills by this author →
GitHub

17th-pr-summary

Generate standardized PR titles and summaries from git diffs and commit history.

Updated Jan 23, 2026
Search Tags:#conventions#commit history#generate#git diff#PR title#PR summary#branch name
One-click install
npx skills add https://github.com/SeventeenthEarth/glm-worker-mcp --skill 17th-pr-summary
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 17th-pr-summary
Source: https://github.com/SeventeenthEarth/glm-worker-mcp/tree/main/skills/17th-pr-summary
Command: npx skills add https://github.com/SeventeenthEarth/glm-worker-mcp --skill 17th-pr-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of PR titles and summaries to ensure consistent formatting across the codebase.

Core Features & Use Cases

  • Analyze git diffs and commit history to derive a concise, actionable PR title and a descriptive summary.
  • Derive an uppercase tag from the current branch (INT for main) and apply it to the title.
  • Enforce project conventions for tone and length, helping reviewers understand changes quickly.

Quick Start

Run the PR summary command on your working tree to generate a title and summary from your staged or committed changes.

Frequently Asked Questions about 17th-pr-summary

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

FAQPage Schema
How do I generate a PR summary from a git diff and commit history?▼

To generate a PR summary, this Skill parses your git diff and commit history to derive a concise title and descriptive summary. It analyzes staged or committed changes on your working tree to produce standardized PR content.

Can I automatically enforce PR title naming conventions from my branch name?▼

Yes, you can enforce PR title naming conventions automatically. The Skill derives an uppercase tag directly from your current branch name, such as INT for main, and applies it to the generated PR title.

What is the best way to format consistent PR titles for code reviewers?▼

The best way to format consistent PR titles is to use a generator that parses commits and applies project guidelines. This ensures your titles maintain correct tone, length, and naming conventions for clear reviewer context.

When do I need to generate a PR title and summary from my feature branch?▼

You need to generate a PR title and summary after implementing changes or before creating a PR. It works on feature branches and main workflows to prepare your commit history and git diff for review.

Do I need staged changes to generate a PR summary?▼

You need either staged or committed changes in your working tree to generate a PR summary. The Skill parses these git diffs alongside your branch and commit history to derive the final PR text.

Related Skills

Explore More Software Engineering Skills→
AleksaRistic216AleksaRistic216

quick-commit

Create concise git commit messages and commit staged changes.

Community
Basic
assertchrisassertchris
2

custom-submit-pr

Create a GitHub pull request with the gh CLI and assign it to assertchris.

Community
Intermediate
hiiamskyhiiamsky

git-conventions

Validate Git commit messages, branch names, and PR descriptions against preset conventions.

Community
Intermediate
robhowleyrobhowley
5

open-pr

Generate pull request titles and descriptions from conventional commit messages.

Community
Intermediate