skills.rest
kagenti
kagentiOFFICIAL
Explore all skills by this author →
GitHub

repo:pr

Enforce standardized GitHub pull request titles and bodies with emoji and issue references.

292|103|Updated Mar 27, 2025
Search Tags:#git#code review#pull request#developer workflow#github#convention
One-click install
npx skills add https://github.com/kagenti/kagenti --skill repo-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo:pr
Source: https://github.com/kagenti/kagenti/tree/main/.claude/skills/repo%3Apr
Command: npx skills add https://github.com/kagenti/kagenti --skill repo-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a consistent and informative format for pull request titles and bodies, improving code review clarity and issue tracking.

Core Features & Use Cases

  • Standardized PR Title: Ensures titles start with an emoji and are descriptive.
  • Structured PR Body: Mandates a 'Summary' section and allows for optional 'Related issue(s)'.
  • Use Case: When creating a pull request for a new feature, this Skill guides you to write a title like "✨ Implement user authentication" and a body that clearly explains the changes and links to the relevant issue, e.g., "Fixes #123".

Quick Start

Use the repo:pr skill to create a pull request with a title and summary.

Frequently Asked Questions about repo:pr

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

FAQPage Schema
How do I standardize GitHub pull request titles and bodies for better code review?▼

To standardize GitHub pull request titles and bodies for better code review, this Skill enforces a consistent format requiring descriptive emoji-led titles and structured body sections with summaries and related issue links.

What is the required format for a pull request title in a developer workflow?▼

The required format for a pull request title in a developer workflow mandates starting with an emoji followed by a descriptive summary, such as using a sparkles emoji to indicate a new feature implementation.

How do I structure a pull request body to link related issues automatically?▼

To structure a pull request body to link related issues automatically, you must include a mandatory 'Summary' section and an optional 'Related issue(s)' section using automated issue linking syntax like 'Fixes #123'.

Does this pull request convention enforcer require any external dependencies?▼

This pull request convention enforcer does not require any external dependencies, allowing you to apply its formatting rules for titles, summaries, and issue references directly within your software development workflow.

Why should I use a standardized PR format for my code review practices?▼

You should use a standardized PR format for your code review practices because it improves clarity and traceability across software development workflows, ensuring changes are well-communicated and automated issue linking functions properly.

Related Skills

Explore More Software Engineering Skills→
naj2rnaj2r

commit

Creates git commits with auto-generated messages and optional push.

Community
Intermediate
tribedotruntribedotrun
8

mando-pr

Create GitHub pull requests and trigger AI reviewers with CI monitoring.

Official
Advanced
korchasakorchasa
3

flow-commit

Automate commit planning and grouping into atomic Conventional Commits.

Community
Advanced
christian289christian289

managing-branch-pr-workflow

Enforce branch naming, commit message formatting, and automated pull request creation.

Community
Intermediate