From 31fcecc0699579de42829175be9b38bd009f0043 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pawe=C5=82=20Pacana?= Date: Sun, 19 Jul 2026 16:29:45 +0200 Subject: [PATCH] Link the source in commit messages when it has a URL * Add a Format rule to reference the article/blog post that informed the change, the guide it follows, or the deciding task/issue/message. * Attribute decisions by link rather than restating them. --- skills/commit/SKILL.md | 1 + 1 file changed, 1 insertion(+) diff --git a/skills/commit/SKILL.md b/skills/commit/SKILL.md index ba6bd25..331e0bb 100644 --- a/skills/commit/SKILL.md +++ b/skills/commit/SKILL.md @@ -17,6 +17,7 @@ description: Create a git commit following project conventions. Use this skill w - Blank line between subject and body. Body wrapped at 72 cols. - Prefer `*` bullet points in the body over prose paragraphs. Hanging indent for wrapped lines. Blank lines between points. - Body explains **why** (and, when non-obvious, **how** and **what effects** — benchmarks, side effects, follow-ups). Skip questions that don't apply. Never restate the diff. +- Link the source when it has a URL: the reference article or blog post that informed the change, the guide or documentation it follows, or the decision behind it (task, issue, message). ## Scope -- 2.51.2