Comms Impact

State what a change means for users and the business in plain words, as "When <who> does <what>, <now>. Before, <then>." Use when writing the impact part of a PR description, change note, changeset, release note, incident summary, or status update, or when someone asks what a change does for users.

23 stars 1 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jpoehnelt/skills --skill comms-impact
Manual install
git clone --depth 1 https://github.com/jpoehnelt/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/comms-impact ~/.claude/skills/comms-impact

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Impact statements

An impact statement tells a reader who never sees the code what changes for whom. It names a person, an action, the new result, and the old result. Work from the observed behavior, since commit messages and file names describe how the author worked.

Repo facts (from AGENTS.md): where impact statements go (PR template section, change notes, changesets, release notes), the product's names for its users and screens, who reads each surface (customers, operators, support, developers), and where usage or support numbers come from, if anywhere.

## Find the behavior

1. List the behavior the change touches from the diff, its tests, and stories: routes, screens, API responses, emails, jobs, limits, error messages. Ignore refactors that change no output.
2. For each behavior, name four things:
   - **Who**: the role in the product's words (signed-in member, workspace admin, API client, on-call operator), not "the user" when a role exists.
   - **Does what**: the action or condition that triggers it, specific enough to reproduce.
   - **Now**: what they see or get after the change.
   - **Before**: what they saw or got on the base branch. Check it there by running it, reading the old code path, or reading the test the change edits. Do not infer it from the PR title.
3. If you cannot establish the old result, write "Before: not verified".

## Write it

Use one statement per behavior:
Read the full skill on GitHub

Details

Skill name
comms-impact
Path
comms-impact/SKILL.md
License
MIT
Repo updated
12 November 2026

FAQ

What does the Comms Impact skill do?

State what a change means for users and the business in plain words, as "When <who> does <what>, <now>. Before, <then>." Use when writing the impact part of a PR description, change note, changeset, release note, incident summary, or status update, or when someone asks what a change does for users.

How do I install the Comms Impact skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jpoehnelt/skills --skill comms-impact. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Comms Impact popular?

It lives in jpoehnelt/skills, which has 23 GitHub stars and 1 forks.

Related skills

Agents Correct

23

jpoehnelt/skills

Find the mistakes agents keep repeating in a repo and make each one impossible, trying architecture first, then types, lint, tests, and docs last. Use when the operator keeps correcting the same mistake, or for /agents-correct.

AI, LLMs & Agents

Agents Create Verification Skill

23

jpoehnelt/skills

Generate a project-local verify skill that drives the app like a user through a browser with Playwright, a CLI, or HTTP. Use for /agents-create-verification-skill, "make a verify skill for this repo", or when a project has no scripted way to prove UI, CLI, or service behavior.

AI, LLMs & Agents

Agents Reflect

23

jpoehnelt/skills

After a work session, review what went wrong and right and turn each lesson into a concrete edit to an existing skill or AGENTS.md line. Use when the user says "reflect" or /agents-reflect.

AI, LLMs & Agents

Eng Change Checklist

23

jpoehnelt/skills

Short checklist of engineering principles to apply before and after non-trivial work. Use when planning or reviewing a non-trivial change, debugging a stubborn failure, designing types or boundaries, or deciding how to sequence a migration.

Productivity & Notes

Alterlab Nmc Data Journalist

21

AlterLab-IEU/AlterLab-FC-Skills

This skill should be used when the user asks about "data journalism", "data visualization", "data storytelling", "FOIA request", "RTI request", "spreadsheet analysis", "chart design", "act as a data journalist", "data journalist mode", "infographic", "open data", "statistical analysis for journalism", "investigative data", "public records", "Datawrapper", "Flourish", "Tableau Public", "D3.js", "chart type selection", or needs expertise in finding, analyzing, and visualizing data for journalistic storytelling. Part of the AlterLab FC Skills collection (New Media & Communication department).

Productivity & NotesIn 1 list

Formatting Notion Pages

9

mattppal/formatting-notion-pages

Apply rich formatting to Notion pages - toggles, callouts, headers, and styled text. Use when creating or formatting Notion documents via the Notion MCP server.

Productivity & Notes

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.