# PR Squash Message

Generate one short Conventional Commits squash message describing only the net diff...

- Repository: https://github.com/scenario-labs/skills (1448 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add scenario-labs/skills --skill pr-squash-message -g -a claude-code -y`
Codex: `npx skills add scenario-labs/skills --skill pr-squash-message -g -a codex -y`
Cursor: `npx skills add scenario-labs/skills --skill pr-squash-message -g -a cursor -y`
Gemini CLI: `npx skills add scenario-labs/skills --skill pr-squash-message -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add scenario-labs/skills`

## Description

Generate one short Conventional Commits squash message describing only the net diff between the PR's base and head, set its header as the PR title, validate it with the repository's commitlint and both copy its description to the clipboard and display it, when asked for a squash message. Works in any Scenario repository, whatever its default branch.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Squash message

One short commit message for the whole PR. It describes the **destination**, the net diff between the PR's base and its head, never the journey: a commit that only repairs code introduced earlier on this branch is invisible to the base branch, so it gets no `fix`, no bullet, no mention. Installed in every repo, so conventions are discovered.

**Untrusted PRs.** Running anything from the branch (checks, tests, commitlint, installs) executes the branch's own code, whichever command you pick, so where the command comes from does not matter. Trust the PR only when `gh api repos/{owner}/{repo}/pulls/<n> --jq '[.head.repo.full_name == .base.repo.full_name, .author_association] | @tsv'` prints `true` and `OWNER`, `MEMBER` or `COLLABORATOR` (a fork or an outside author fails). On an untrusted PR, run nothing from the branch without asking: say what you skipped and ask first.

GitHub's squash dialog takes the subject from the PR title and the description from what you paste. So the header goes in the PR title and the clipboard gets the description only. Release-please starts a new changelog entry at every blank line followed by `type(scope): `, so a description that opens with the header logs the change twice.

The rest: https://github.com/scenario-labs/skills/blob/HEAD/.agents/skills/pr-squash-message/SKILL.md