// 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.
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.
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.
Validate commit messages against the Conventional Commits specification. Auto-detects and installs commitlint CLI if missing. Checks project config or falls back to sensible defaults. Use when validating commit messages, preparing PRs, or enforcing commit conventions.
Audit Go nolint directives for staleness and lazy justifications. Mechanically verifies each suppression with golangci-lint, then runs adversarial Red/Blue/White debates on the top candidates for removal. Use when inheriting a Go codebase, during periodic cleanup, or when nolint count is growing unchecked.
Validate markdown files against formatting standards. Auto-detects and installs markdownlint-cli if missing. Checks project config or falls back to sensible defaults. Supports auto-fix mode. Use when creating or modifying markdown files, validating documentation, or enforcing markdown conventions.
Strategic roadmap management for GitHub repositories. Syncs ROADMAP.md with GitHub Issues and labels, bootstraps roadmap files from scratch, runs brainstorming sessions with boundary checking, and provides quick status summaries. Use when managing project planning, syncing roadmap state, or exploring feature ideas.
| name | pull-request-msg-with-gh |
| description | 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. |
| compatibility | Requires GitHub CLI (gh) authenticated with the target repository. |
Generate a PR_MESSAGE.md file summarizing the current session's work.
Requires gh CLI authenticated with the target repository.
gh --version 2>/dev/null && gh auth status 2>/dev/null
If gh is not installed, stop and report:
gh cannot be installed via npmgh auth login to authenticateDo not proceed without a working, authenticated gh CLI.
git diff and git status to
understand the full scope of work, in addition to reviewing
conversation history. Both sources inform the PR message.Closes #<issue-number> footer entirely.references/pr-message-format.md for the list of types)references/pr-message-format.mdPR_MESSAGE.md if not already presentThe issue number MUST be determined by searching GitHub, NOT by extracting numbers from branch names.
# 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
125- is NOT issue #125)specs/125-xyz/)These are internal identifiers, not GitHub issue numbers.
## Commit Message section — the first line IS the commit
message.markdownlint.json — use CLI flags insteadIf 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:
npm install -g @commitlint/cli @commitlint/config-conventionalnpm install -g markdownlint-cliDo not silently skip validation.
Fix any issues and re-validate before reporting success.