skills.rest
rshade
rshadeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pull-request-msg-with-gh

Generate a structured PR_MESSAGE.md for GitHub pull requests using gh.

3|Updated Mar 18, 2026
Search Tags:#automation#github#pr#gh#code-review#pull-request#session-context
One-click install
npx skills add https://github.com/rshade/agent-skills --skill pull-request-msg-with-gh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-request-msg-with-gh
Source: https://github.com/rshade/agent-skills/tree/main/skills/pull-request-msg-with-gh
Command: npx skills add https://github.com/rshade/agent-skills --skill pull-request-msg-with-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of a PR_MESSAGE.md by summarizing session work and tying it to an issue when applicable.

Core Features & Use Cases

  • Generate a structured PR_MESSAGE.md with subject, summary, test plan, and changelog based on the current session.
  • Detect related issues via branch keywords or session context and link them in the PR description.
  • Validate the PR_MESSAGE.md with commitlint and markdownlint when those tools are available in the environment.
  • Ensure the GitHub CLI (gh) is authenticated before proceeding and fail gracefully if not.

Quick Start

Generate a PR_MESSAGE.md from the current session context using gh.

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 auto-generate a PR message from session context for GitHub?▼

You can auto-generate a PR message from session context by analyzing current session changes, detecting related issues via branch keywords, and composing a structured PR_MESSAGE.md with subject, summary, test plan, and changelog sections.

What is the best way to create a structured pull request description automatically?▼

The best way to create a structured pull request description automatically is to summarize session work and link detected related issues, producing a PR_MESSAGE.md that includes a subject, summary, test plan, and changelog for GitHub pull requests.

Do I need GitHub CLI authentication to generate a PR_MESSAGE.md?▼

Yes, you need GitHub CLI (gh) authentication to generate a PR_MESSAGE.md. The process ensures gh is authenticated before proceeding and fails gracefully if the GitHub CLI is not properly authenticated.

Can I validate a generated PR message with commitlint and markdownlint?▼

Yes, you can validate the generated PR_MESSAGE.md with commitlint and markdownlint. When these linting tools are available in the environment, the PR message generation process automatically validates the markdown output.

How does detecting related issues work when generating a pull request description?▼

Detecting related issues works by analyzing branch keywords or session context to identify linked issues, which are then automatically referenced and linked in the structured PR_MESSAGE.md description for the GitHub pull request.

What limitations exist when automating PR message creation from session context?▼

Limitations of automating PR message creation include the requirement of GitHub CLI authentication, dependency on available commitlint and markdownlint tools for validation, and the need for detectable branch keywords or session context to link related issues.

Related Skills

Explore More Software Engineering Skills→
serejarisserejaris
215

gh-issues

Manage GitHub Issues via gh CLI with JSON and jq scripting.

Community
Advanced
SamyakJhaveriSamyakJhaveri

pr

Push a local feature branch and create a GitHub pull request.

Community
Intermediate
rshadershade
3

commitlint

Validate commit messages against the Conventional Commits specification.

Community
Intermediate
ricardorochericardoroche
2

git-workflow-standards

Enforce conventional commits, branch naming, PR templates, and semantic versioning.

Community
Intermediate