GitHub, Git & DevOps · IN-DEPTH PROFILE

commit-message-storyteller

Narrative Conventional Commit messages that explain intent, impact, and logical change boundaries.

View listed source ↗Installation guide ↓
Best for

Developers maintaining readable project history

What you get

Infer change intent + Write the commit story

Main limitation

A diff often cannot reveal the true motivation, user impact, or issue context.

First risk

Incorrect intent inferred from code. The generated narrative may confidently attribute a reason the diff does not establish. Confirm the motivation, issue reference, scope, and breaking-change status before committing.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-08-20

Pinned revision · 318066d2

Open pinned commit ↗
SkillSignal profileEditorial metadata

Updated 2026-08-20

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

30-SECOND BRIEF

What it does—and when it fits

Commit Message Storyteller is a GitHub Awesome Copilot workflow that turns diffs or change descriptions into Conventional Commit messages explaining why a change exists, what problem it solves, and whether the diff should be split into multiple logical commits.

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project scope.agents/skills/commit-message-storyteller/
Personal scope~/.copilot/skills/commit-message-storyteller/

Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.

Install command (project scope)npx skills add github/awesome-copilot --skill commit-message-storyteller --agent github-copilot
Official agent docs

Copilot also accepts .github/skills and .claude/skills at project scope. Preview untrusted Skills before enabling scripts.

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Infer change intent

Read the diff to identify what changed, why, and the affected scope.

02

Write the commit story

Create an imperative subject plus optional rationale and issue references.

03

Recommend splits

Separate unrelated concerns when one diff contains several logical changes.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. Improves commit history by preserving intent rather than restating filenames.
  2. Handles breaking changes, issue references, and logically separate work.

Limitations

  1. A diff often cannot reveal the true motivation, user impact, or issue context.
  2. The Skill drafts messages but does not itself prove the changes are tested or safe to commit.

COMPARE THE TRADEOFF

Consider these close alternatives

These are deterministic nearby candidates, not paid placements or a universal ranking. Open the full profile before choosing.

01

Same job family · native to GitHub Copilot

pr-screenshots

Matched before-and-after visual evidence for pull requests, including upload and sizing guidance.
Tradeoff to check
GitHub has no clean public API for PR-description image upload in this workflow.
First risk
Sensitive data in shared screenshots · High
Source state
Pinned · 318066d2
Open profile ↗
02

Same job family

supply-chain-risk-auditor

Measured dependency risk reports covering advisories, maintainers, abandonment, and install scripts.
Tradeoff to check
Does not fully parse yarn.lock, pnpm-lock.yaml, poetry.lock, or unsupported ecosystems.
First risk
Registry and repository metadata exposure · High
Source state
Pinned · 9b281335
Open profile ↗
03

Same job family

appinsights-instrumentation

AppInsights Instrumentation is a reference Skill for adding Azure Application Insights telemetry patterns and SDK configuration to supported web applications.
Tradeoff to check
It is guidance only; requests to add or change components must route to Azure Prepare.
First risk
Sensitive or excessive telemetry · High
Source state
Pinned · ea76537e
Open profile ↗
Compare more in the directory →

BEST FIT

Who it is for

→

Developers maintaining readable project history

→

Teams standardizing Conventional Commit messages

BEFORE YOU USE IT

Risks to review before use

Medium

Incorrect intent inferred from code

The generated narrative may confidently attribute a reason the diff does not establish. Confirm the motivation, issue reference, scope, and breaking-change status before committing.

SECURITY

What the permission profile means

  • Review diffs for secrets before pasting them into external chat services.
  • Do not include confidential issue details in public commit history.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream package contentSource-linked
references/conventional-commits-guide.mdUpstream package contentSource-linked

TAGS

gitconventional-commitswriting

Original SkillSignal editorial profile grounded in GitHub Awesome Copilot commit 318066d2, checked 2026-08-20; not independently executed or security-certified.