Skip to content
Skills Library
Programming · Writing

comms-pr

/comms-pr

Use when drafting or updating a Flowstate pull request title and body; the body follows the template's six sections and the commit-conventions check reads it.

Repository
flowstate ↗
Licence
MIT
Last repository change
23.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when drafting or updating a Flowstate pull request title and body; the body follows the template's six sections and the commit-conventions check reads it.

Original author description

Use when drafting or updating a Flowstate pull request title and body; the body follows the template's six sections and the commit-conventions check reads it.

How it works

  1. Default shape
  2. What the conventions check reads
  3. Repository specifics
  4. Attribution
Original SKILL.md headings · 52 lines, 372 words
SKILL.md preview
---
name: comms-pr
description: Use when drafting or updating a Flowstate pull request title and body; the body follows the template's six sections and the commit-conventions check reads it.
---

# Pull request communication

A PR body makes the change reviewable without restating the diff. Gather the
base/head diff, commits, the linked issue or decision, generated artifacts, and
the command results, and treat them as authoritative over recollection. If the
branch moved, refresh them before editing the body.

## Default shape

1. **Why** — the problem, decision, or missing capability this change addresses.
2. **What changed** — the behavioral shape and the important boundaries, not a
   list of files.
3. **Design choices** — only non-obvious choices a reviewer must evaluate,
   including alternatives deliberately refused.
4. **Verification** — exact checks that completed and the behavior they prove.
5. **Risk, compatibility, and rollout** — where the change can fail, what remains
   compatible, and any migration or operational consequence.
6. **Remaining uncertainty** — checks not run, known limitations, or follow-up
   work that is intentionally outside this PR.

These are the `##` headings of `.github/PULL_REQUEST_TEMPLATE.md`; a test keeps
the two lists equal. A small change has a small body; use tables, examples, or
mutation evidence only when they materially reduce the reviewer's work.

## What the conventions check reads

`tools/commitcheck` runs on the title and body (`commitcheck.yml` passes
`-strict`, so a finding fails the check); the squash message at merge time owes
the title shape, the absolute-claim rule, and the length bound, but no issue or
verification record:

- Title: `scope: lowercase imperative`.
- Body, pull request only: an issue reference (`Refs #N`, `Closes #N`) or a `No-Issue: <reason>`
  trailer, and a `## Verification` heading or `Verification:` line, or an
  `Unverified: <reason>` trailer.
- "fully tested", "safe", "backward-compatible", and "no impact" must sit on a
  line that also carries their evidence.

## Repository specifics

- Do not hard-wrap GitHub prose; keep each paragraph and list item on one source
  line and let the browser wrap it.
- Distinguish a local pass from CI, and a targeted check from the full gate. A
  skipped or unavailable check is named as such, not omitted.

## Attribution

A footer or session link the host or the forge adds to a body is permitted and
never required; the check does not read either. Review comments and replies are the
exception: nothing appends a footer there, so those carry it explicitly.

Versions

The database has no other skills named comms-pr.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 22f194301a1b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100comms-issue
    Use when drafting or updating a Flowstate GitHub issue or design proposal, so it lands as a durable problem statement with evidence and acceptance criteria rather than a transcript.
  • 90comms-commit
    Use when writing or reviewing a Flowstate commit message or squash subject; the shape is a scope prefix, a colon, and a lowercase imperative, with a body that says why, and tools/commitcheck holds it to that shape.
  • 100write-pr
    Draft a pull request title and body from the current branch's diff and commit history, following the project's PR template and title conventions. Use when the user is about to open a PR and wants ready-to-paste content, or asks to write, draft, or fill in a PR description.…
  • 92writing-pr
    Use when writing or editing a pull request title or body.
  • 100pr
    Write or update a pull request body from the repo's PR template, with evidence and validation traced to commands actually run. Use when writing or updating a PR body. To open the PR itself, use file-pr.
  • 92pr
    Use when writing a PR body.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.