Skip to content
cccskills
FreePublished on GitHub

pull-request-msg-with-gh

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.

The English summary is being prepared. Showing the original description.

dirien/yet-another-agent-harness
Works withGitHub
See how to install

Files included (2)

  • SKILL.md3.9 KB
  • references/pr-message-format.md1.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

<!-- Copyright 2025-2026 Richard Shade. Licensed under Apache-2.0. --> <!-- SPDX-License-Identifier: Apache-2.0 -->

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

  1. 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.
  2. 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.
  3. Determine commit type — based on the nature of changes (see references/pr-message-format.md for the list of types)
  4. Write PR_MESSAGE.md — using the format in references/pr-message-format.md
  5. Add to .gitignore — add PR_MESSAGE.md if not already present
  6. 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

  1. Exactly 1 result with title containing most keywords → use it
  2. 0 results → ask the user for the issue number
  3. 2+ results → show options and ask the user to pick
  4. 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

  1. No redundancy — summary must add context beyond the commit subject
  2. No ## Commit Message section — the first line IS the commit message
  3. Never modify .markdownlint.json — use CLI flags instead
  4. Trailing newline — file must end with a single newline
  5. 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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

agent-ready-go

Free

Prepares Go applications to work effectively with AI coding agents. Use when setting up a new Go project or retrofitting an existing one to ensure: structured JSON logging (slog/Zap/ZeroLog/Logrus), machine-readable command output, thorough golangci-lint configuration, non-interactive CLI design with --yes flags, structured error handling with meaningful exit codes, proper context.Context propagation, graceful shutdown, health check endpoints, and a standardized Makefile. Triggers when a user asks to make their Go app "agent-ready," "AI-friendly," wants to improve agent tooling/observability in a Go project, or needs to audit an existing Go project against agent-readiness best practices.

The English summary is being prepared. Showing the original description.

dirien/yet-another-agent-harness20Updated May 31, 2026

agent-rules

Free

Use when creating or updating AGENTS.md files, .github/copilot-instructions.md, or other AI agent rule files, onboarding AI agents to a project, standardizing agent documentation, or when anyone mentions AGENTS.md, agent rules, project onboarding, or codebase documentation for AI agents.

The English summary is being prepared. Showing the original description.

dirien/yet-another-agent-harness20Updated May 31, 2026

architecture-designer

Free

Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.

The English summary is being prepared. Showing the original description.

dirien/yet-another-agent-harness20Updated May 31, 2026

cli-developer

Free

Use when building CLI tools, implementing argument parsing, or adding interactive prompts. Invoke for parsing flags and subcommands, displaying progress bars and spinners, generating bash/zsh/fish completion scripts, CLI design, shell completions, and cross-platform terminal applications using commander, click, typer, or cobra.

The English summary is being prepared. Showing the original description.

dirien/yet-another-agent-harness20Updated May 31, 2026

cloudformation-to-pulumi

Free

Convert an AWS CloudFormation stack or template to Pulumi. This skill MUST be loaded whenever a user requests migration or conversion of CloudFormation to Pulumi.

The English summary is being prepared. Showing the original description.

dirien/yet-another-agent-harness20Updated May 31, 2026

code-reviewer

Free

Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues. Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quality. Complements specialized skills (security-reviewer, test-master) by providing broad-scope review across correctness, performance, maintainability, and test coverage in a single pass.

The English summary is being prepared. Showing the original description.

dirien/yet-another-agent-harness20Updated May 31, 2026

See all skills by dirien

Report a problem with this skill