commit-message-storyteller

tarafından github

Git farklarını veya aşamalı değişiklikleri analiz eder ve yalnızca neyin değiştiğini değil, bir değişikliğin NEDEN yapıldığını açıklayan anlatısal commit mesajları oluşturur — Conventional… kurallarına uygun olarak.

npx skills add https://github.com/github/awesome-copilot --skill commit-message-storyteller

ZIP İndir GitHub

35.8k

Commit Message Storyteller

Transforms raw git diffs and change descriptions into clear, story-driven commit messages that follow the Conventional Commits specification. Instead of "update file.js", you get messages that communicate intent, context, and impact.

When to Use This Skill

User says "write a commit message", "help me commit", or "generate a commit"
User pastes a git diff or describes code changes
User says "what should I commit this as?" or "summarize my diff"
User wants better commit history for their team or open-source project
User is preparing a pull request and wants meaningful commit messages

Prerequisites

Have at least one of the following ready:

Output from git diff or git diff --staged
A description of what you changed and why
A list of modified files

How It Works

Step 1: Gather the Change Context

Ask the user (or infer from the diff) for:

What changed — files, functions, logic affected
Why it changed — bug fix, new feature, refactor, performance, etc.
Who/what triggered it — issue number, user request, tech debt, etc.

If the user provides a raw git diff, extract this context automatically from the diff.

Step 2: Identify the Commit Type

Map the change to a Conventional Commits type using this guide:

Type	Use When
`feat`	A new feature or capability is added
`fix`	A bug or incorrect behavior is corrected
`refactor`	Code restructured without changing behavior
`perf`	A change that improves performance
`docs`	Documentation only changes
`style`	Formatting, whitespace, missing semicolons (no logic change)
`test`	Adding or updating tests
`chore`	Build process, dependency updates, config changes
`ci`	CI/CD pipeline changes
`revert`	Reverting a previous commit

See references/conventional-commits-guide.md for detailed examples.

Step 3: Write the Commit Message

Follow this structure:

<type>(<optional scope>): <short imperative summary>

<body — the story: why this change was made, what problem it solves>

<footer — issue refs, breaking change notices>

Rules for Each Part

Subject line (first line):

Use imperative mood: "add", "fix", "remove" — not "added" or "fixes"
Max 72 characters
No period at the end
Lowercase after the colon

Body (the story):

Explain the why, not the what (the diff already shows the what)
Describe the problem that existed before this change
Mention any alternatives considered if relevant
Keep lines under 100 characters
Separate from subject with a blank line

Footer:

Reference issues: Closes #123, Fixes #456, Refs #789
Mark breaking changes: BREAKING CHANGE: <description>

Step 4: Generate Output

Produce the commit message in a copyable code block, followed by a one-line plain-English explanation of the story you told.

Example output:

fix(auth): prevent token refresh loop on expired sessions

When a user's session expired mid-request, the auth middleware was
triggering a token refresh, which itself failed validation and triggered
another refresh — causing an infinite retry loop that crashed the app.

This adds a recursion guard flag that aborts the refresh cycle if a
refresh is already in progress, returning a clean 401 instead.

Closes #312

Story told: A silent infinite loop on session expiry was crashing the app; this stops the cycle early and returns a clean error.

Multiple Commits from One Diff

If the diff contains logically separate changes, split them into multiple commit messages and tell the user. Use this heuristic:

Different files with unrelated purposes → likely separate commits
Same file but distinct concerns (e.g., bug fix + refactor) → suggest splitting
Everything tightly coupled → one commit is fine

Edge Cases

Situation	How to Handle
User provides no context beyond a diff	Infer type and scope from file names and changed symbols
Changes span many files with no clear theme	Ask: "Is this one logical change, or multiple?"
Breaking change detected	Add `BREAKING CHANGE:` footer automatically
User says "keep it short"	Omit body, just write a strong subject line
No issue number available	Omit the footer entirely

Quick Reference

# Get your staged diff to paste into Copilot
git diff --staged

# Or get the last uncommitted working tree changes
git diff

See references/conventional-commits-guide.md for type examples and scope guidelines.

github tarafından daha fazla skill

console-rendering

github

Go'da struct etiketi tabanlı konsol renderlama sistemini kullanma talimatları

official

acquire-codebase-knowledge

github

Bu beceriyi, kullanıcı açıkça mevcut bir kod tabanını haritalamayı, belgelemeyi veya bu kod tabanına dahil olmayı istediğinde kullanın. "Bu kod tabanını haritala", "belgele…" gibi ifadeler için tetikleyin.

official

acreadiness-assess

github

Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc…

official

acreadiness-generate-instructions

github

AgentRC talimatları komutu aracılığıyla özelleştirilmiş AI ajan talimat dosyaları oluşturur. .github/copilot-instructions.md dosyasını üretir (varsayılan, VS'de Copilot için önerilir…

official

acreadiness-policy

github

Kullanıcının bir AgentRC politikası seçmesine, yazmasına veya uygulamasına yardımcı olun. Politikalar, ilgisiz kontrolleri devre dışı bırakarak, etki/seviyeyi geçersiz kılarak, ayarlayarak…

official

add-educational-comments

github

We need to translate the given English text into Turkish, preserving the name "add-educational-comments" if it appears. The text is a description of an agent skill. We must not add any extra commentary, labels, or formatting. The translation should be accurate and natural in Turkish. The text: "Add educational comments to code files to transform them into effective learning resources. Adapts explanation depth and tone to three configurable knowledge levels: beginner, intermediate, and advanced Automatically requests a file if none is provided, with numbered list matching for quick selection Expands files by up to 125% using educational comments only (hard limit: 400 new lines; 300 for files over 1,000 lines) Preserves file encoding, indentation style, syntax correctness, and..." It seems cut off at the end. The original might have more, but we only have this. We'll translate what's given. Note: The name "add-educational-comments" does not appear in the text, so we don't include it. Translation: "Kod dosyalarına

official

adobe-illustrator-scripting

github

ExtendScript (JavaScript/JSX) kullanarak Adobe Illustrator otomasyon betiklerini yazın, hata ayıklayın ve optimize edin. Oluştururken veya değiştirirken kullanın…

official

agent-governance

github

Yapay zeka aracı erişimi ve davranışını kontrol etmek için bildirimsel politikalar, niyet sınıflandırması ve denetim izleri. Birleştirilebilir yönetişim politikaları, izin verilen/engellenen araçları, içerik filtrelerini, hız sınırlarını ve onay gereksinimlerini tanımlar — kod değil yapılandırma olarak saklanır. Anlamsal niyet sınıflandırması, araç yürütülmeden önce desen tabanlı sinyaller kullanarak tehlikeli istemleri (veri sızdırma, ayrıcalık yükseltme, istem enjeksiyonu) tespit eder. Araç düzeyinde yönetişim dekoratörü, politikaları işlevde u

official