comms-commit

What it does and when to use it

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.

How it works

1. Shape
2. Attribution

---
name: comms-commit
description: 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.
---

# Commit communication

Write for the future reader deciding what changed, why, and whether the commit
belongs in the history. Read the staged diff and the verification that actually
completed; do not write from the conversation's memory when the tree can answer.

## Shape

- Subject: `scope: lowercase imperative`, the scope an area of the tree
  (`engine: bound the walker's depth`), specific enough to distinguish the
  commit from its neighbors.
- Body only when the motivation, a compatibility or security choice, a
  non-obvious mechanism, or the verification cannot fit honestly in the subject.
  Explain the decision and its consequence, not a file-by-file tour of the diff
  or a diary of how the agent got there.
- Name a limitation or an unverified leg when it changes how the commit should
  be reviewed or used. Do not claim a test, review, or generated check ran unless
  its result is in hand.
- A squash message is held to the subject shape, the absolute-claim rule
  ("safe", "fully tested" need evidence on their line), and a length bound; the
  pull request body carries the issue reference and the verification, so the
  message needs neither. `tools/commitcheck` reports a subject that is not
  `scope: lowercase imperative`.

## Attribution

A trailer the host adds (`Co-Authored-By`, a session link) is permitted and
never required; `tools/commitcheck` does not read it. A `Co-Authored-By` trailer
is for crediting a second contributor, a person who paired on the change or
another agent that wrote part of it, rather than the model that happened to
serve the turn.

Versions

The database has no other skills named comms-commit.

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

Database snapshot: 13.11.2026 · package version f609882638ed (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-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.
• 100squash-commit
  Write a Conventional-Commits squash commit message for a finitevolX pull request from its commits and description. Use when asked for a squash / merge commit message.
• 100pr-commit-message
  Write or improve high-signal PR merge commit messages and squash commit messages. Use this whenever the user says "create a commit message for this PR", "write a merge commit message", "draft the squash commit body", "improve this commit message", or asks for a message that…
• 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.
• 100commit-message-writing
  Use this skill when the user explicitly asks to generate, write, draft, or create a commit message, squash commit, commit title, or merge commit message for the Shopware core repository (shopware/shopware). Supports two modes — full commit messages (title + body) for branch…
• 100comms-how
  Explain how a subsystem works, its architecture, runtime flow, and where new code belongs. Use for "how does X work", walkthroughs before changing something, and placement or ownership questions like "where should this live" or "which package owns this". Use comms-why for motivation.