pull-request-msg-with-gh

Generate a structured PR_MESSAGE.md from git changes and GitHub CLI queries.

19|3|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/dirien/yet-another-agent-harness --skill pull-request-msg-with-gh-dirien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull-request-msg-with-gh
Source: https://github.com/dirien/yet-another-agent-harness/tree/main/.claude/skills/pull-request-msg
Command: npx skills add https://github.com/dirien/yet-another-agent-harness --skill pull-request-msg-with-gh-dirien

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generating clear, consistent, and reviewer-friendly pull request descriptions is often manual, inconsistent, and missing links to related issues; this Skill automates creation of a structured PR_MESSAGE.md so the PR has a proper subject, summary, test plan, changes list, and issue footer when applicable.

Core Features & Use Cases

  • Analyze the current session and repository state to summarize changes and derive a commit-style subject line.
  • Detect related GitHub issues by searching issue titles using branch keywords, prompt the user when ambiguous, and include a Closes footer when appropriate.
  • Produce a PR_MESSAGE.md formatted with Summary, Test plan, and Changes sections and validate the output with commitlint and markdownlint; add PR_MESSAGE.md to .gitignore if needed.
  • Use case: preparing a pull request from local changes before pushing, ensuring reviewers get a concise, validated description and associated issue reference.

Quick Start

Generate a PR_MESSAGE.md for the current session using the authenticated GitHub CLI, run commitlint and markdownlint to validate it, and present the final file for review.

Frequently Asked Questions about pull-request-msg-with-gh

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

FAQPage Schema
How do I generate a GitHub pull request message from local git changes?

Generate a structured GitHub pull request message by analyzing local git changes and querying related issues via keyword search. This Skill creates a validated PR_MESSAGE.md containing a summary, test plan, changes list, and issue footer.

Do I need the GitHub CLI to create a validated pull request description?

Yes, you need an authenticated GitHub CLI (gh) to generate a validated pull request description. The tool queries GitHub issues using branch keywords and applies commitlint and markdownlint validation to the output.

What is the best way to link related GitHub issues in a pull request message?

Link related GitHub issues by searching issue titles with branch keywords and adding a Closes footer to the PR message. When matches are ambiguous, you are prompted to confirm the correct issue before generating the file.

How to validate a pull request message with commitlint and markdownlint?

Validate a pull request message with commitlint and markdownlint by generating a PR_MESSAGE.md that follows the repository's commit type and formatting rules. The validation runs automatically after analyzing local git changes.

Does generating a PR_MESSAGE.md file interfere with my repository commit history?

No, generating a PR_MESSAGE.md does not interfere with your repository commit history. The Skill adds PR_MESSAGE.md to .gitignore if needed, ensuring the generated pull request description file remains untracked.

Can I use commitlint rules to format pull request messages for GitHub repositories?

Yes, you can use commitlint rules to format pull request messages. The Skill derives a commit-style subject line from local changes and validates the entire PR_MESSAGE.md against the repository's specific commit type and PR formatting rules.