skills.rest
this-is-tobi
this-is-tobiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pull-request

Generate structured markdown pull request descriptions with template detection.

5|2|Updated Apr 2, 2023
Search Tags:#automation#git#template#github#pull-request#pr-description
One-click install
npx skills add https://github.com/this-is-tobi/tools --skill pull-request-this-is-tobi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/this-is-tobi/tools/tree/main/copilot/skills/pull-request
Command: npx skills add https://github.com/this-is-tobi/tools --skill pull-request-this-is-tobi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It automates the creation of detailed, standardized pull request descriptions, removing the manual effort of drafting comprehensive PR documentation.

Core Features & Use Cases

  • Template Detection: Checks common repository locations for existing PR templates and uses them when present.
  • Structured Generation: Produces a markdown PR description with sections for summary, purpose, changes, testing, screenshots, breaking changes, and a checklist.
  • Size Guidance: Includes guidelines for estimating review effort based on lines changed.
  • Use Cases: Ideal for developers preparing PRs in GitHub, GitLab, or similar platforms who need consistent, review‑ready documentation.

Quick Start

Ask the pull-request skill to write a PR description for the latest changes in my feature branch.

Frequently Asked Questions about pull-request

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

FAQPage Schema
How do I generate a standardized pull request description for my feature branch?▼

To generate a standardized pull request description, the skill drafts markdown content covering summary, purpose, changes, testing, and breaking changes. It checks your Git repository for existing PR templates and uses them if present.

What sections should be included in a comprehensive GitHub PR description?▼

A comprehensive GitHub PR description should include sections for summary, purpose, changes, testing details, screenshots, breaking changes, and a checklist. This ensures review-ready documentation across Git repositories.

Does the PR generation process detect and use existing repository PR templates?▼

Yes, the PR generation process detects existing PR templates by checking common repository locations. It applies your custom template before drafting standardized markdown content for the pull request.

Can I automate PR documentation for Git repositories to include review effort guidelines?▼

Yes, you can automate PR documentation to include size guidance and review effort guidelines based on lines changed. This standardizes the markdown structure for developers preparing pull requests.

What is the best way to ensure consistent pull request templates across multiple Git platforms?▼

The best way to ensure consistent pull request templates is to automate generation using a standardized markdown structure. This produces review-ready documentation for GitHub, GitLab, or similar platforms by checking for existing templates.

Related Skills

Explore More Software Engineering Skills→
funsaizedfunsaized
1

update-pr-summary

Update PR titles and descriptions from a complete branch diff.

Community
Intermediate
D0NMEGAD0NMEGA
8

gsd-ship

Push a branch, create a PR with an auto-generated body, and track merge status.

Community
Advanced
srirajksrirajk

Git Risk Analysis

Analyze git history to produce a structured PR risk profile.

Community
Advanced
brainbrewlabsbrainbrewlabs
7

doc-publishing

Publishes documentation to GitHub Pages, Vercel, or Netlify from source docs and build outputs.

Official
Intermediate