Pull request msg with gh

Skill rshade/agent-skills/skills/pull-request-msg-with-gh

Picks and Shovels for digging AI

Install

npx -y skills add rshade/agent-skills --skill pull-request-msg-with-gh

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generate a PR_MESSAGE.md file from session context using GitHub CLI. Detects related issues via branch-keyword search, writes a structured PR description with commit subject, summary, test plan, and changelog. Validates with commitlint and markdownlint. Use when preparing a pull request on GitHub.

SKILL.md

3.9 KB, as published. Nobody here has run it

Pull Request Message Generator

Generate a PR_MESSAGE.md file summarizing the current session's work. Requires gh CLI authenticated with the target repository.

Prerequisite check

gh --version 2>/dev/null && gh auth status 2>/dev/null

If gh is not installed, stop and report:

Install from https://cli.github.com
gh cannot be installed via npm
After install, run gh auth login to authenticate

Do not proceed without a working, authenticated gh CLI.

Workflow

Analyze session context — review changes made in the current session. Explore changed files with git diff and git status to understand the full scope of work, in addition to reviewing conversation history. Both sources inform the PR message.
Detect issue number — use the issue detection algorithm below. If the user indicates there is no associated issue, omit the Closes #<issue-number> footer entirely.
Determine commit type — based on the nature of changes (see references/pr-message-format.md for the list of types)
Write PR_MESSAGE.md — using the format in references/pr-message-format.md
Add to .gitignore — add PR_MESSAGE.md if not already present
Validate — run commitlint and markdownlint checks

Issue number detection

The issue number MUST be determined by searching GitHub, NOT by extracting numbers from branch names.

Algorithm

# Step 1: Get branch name
BRANCH=$(git branch --show-current)

# Step 2: Extract keywords (strip leading numbers and hyphens)
# Example: "125-greenops-equivalencies" → "greenops equivalencies"
KEYWORDS=$(echo "$BRANCH" | sed 's/^[0-9]*-//' | tr '-' ' ')

# Step 3: Search GitHub issues
gh issue list --search "$KEYWORDS" --state all \
  --json number,title --limit 5

Evaluation rules

Exactly 1 result with title containing most keywords → use it
0 results → ask the user for the issue number
2+ results → show options and ask the user to pick
Ambiguous match → ask the user to confirm

Never extract issue numbers from

Branch name digits (e.g., 125- is NOT issue #125)
Spec folder names (e.g., specs/125-xyz/)
Worktree folder names

These are internal identifiers, not GitHub issue numbers.

Critical rules

No redundancy — summary must add context beyond the commit subject
No ## Commit Message section — the first line IS the commit message
Never modify .markdownlint.json — use CLI flags instead
Trailing newline — file must end with a single newline
Ask when ambiguous — if issue search returns 0, 2+, or unclear results, ask the user

Validation

If the commitlint and markdownlint skills are available in the current context, use them to validate PR_MESSAGE.md. Otherwise, run directly:

# Validate commit message format
cat PR_MESSAGE.md | npx commitlint

# Validate markdown (MD041 disabled — first line is commit subject,
# not heading)
npx markdownlint --disable MD041 -- PR_MESSAGE.md

If neither the skills nor npx are available, fail hard:

Install commitlint: npm install -g @commitlint/cli @commitlint/config-conventional
Install markdownlint: npm install -g markdownlint-cli

Do not silently skip validation.

Fix any issues and re-validate before reporting success.