skills.rest
tdhopper
tdhopperCOMMUNITY
Explore all skills by this author →
Website𝕏@tdhopperGitHub

creating-pull-requests

Create pull requests with active-voice titles and Why/Approach/How descriptions.

22|5|Updated Jan 9, 2018
Search Tags:#workflow#documentation#collaboration#pr#code-review#pull-requests#gh-cli
One-click install
npx skills add https://github.com/tdhopper/dotfiles2.0 --skill creating-pull-requests-tdhopper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: creating-pull-requests
Source: https://github.com/tdhopper/dotfiles2.0/tree/main/.claude/skills/creating-pull-requests
Command: npx skills add https://github.com/tdhopper/dotfiles2.0 --skill creating-pull-requests-tdhopper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create well-structured pull requests with clear titles and comprehensive descriptions.

Core Features & Use Cases

  • PR Title & Description Formatting: Enforces active-voice titles and a description structure (Why, Approach, How) with context links.
  • Drafting & Automation: Supports drafting descriptions or running gh pr create to streamline PR creation.
  • Compliance Rules: Prevents inclusion of disallowed phrases and coauthor headers to maintain clean commit history.

Quick Start

Draft a pull request with an active-voice title and a description explaining the problem, approach, and context links.

Frequently Asked Questions about creating-pull-requests

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

FAQPage Schema
How do I create a well-structured pull request with a clear description?▼

To create a well-structured pull request, use an active-voice title and a description body structured around Why, Approach, and How, including links to relevant tickets or discussions for context.

What's the best way to automate PR creation using gh cli?▼

Automating PR creation with gh cli is streamlined by automatically generating descriptions that enforce active-voice titles and a structured Why, Approach, How format to maintain clear commit history.

What should be included in a pull request description for better code review?▼

A pull request description for better code review should include a Why, Approach, and How structure, use active voice, and reference relevant tickets or discussions to provide full context.

Does this PR workflow prevent coauthor headers in commit history?▼

Yes, this PR workflow enforces compliance rules that prevent the inclusion of disallowed phrases and coauthor headers to maintain a clean and standardized commit history.

Can I draft pull requests across multiple repositories with structured formatting?▼

Yes, you can draft pull requests across repositories by applying structured descriptions with clear titles, context links, and a standardized Why, Approach, How format during generation.

Why use an active-voice title for a GitHub pull request?▼

Using an active-voice title for a GitHub pull request ensures clear, direct communication of the change, pairing with a comprehensive Why, Approach, How description to improve review readability.

Related Skills

Explore More Software Engineering Skills→
georgekhananaevgeorgekhananaev
27

github-cli

Wrap GitHub CLI commands with risk classification and confirmation prompts.

Community
Intermediate
luanluan
4

resume-work

Recover development context for a branch or pull request after inactivity.

Community
Intermediate
mathiasbourgoinmathiasbourgoin
2

git-conventions

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

Community
Intermediate
bogaboga

creating-pull-requests

Create pull requests with active-voice titles and structured markdown sections.

Community
Intermediate