feat(skills): add commit-message-storyteller skill

[kwekudzata]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• I have read and followed the Guidance for submissions involving paid services.
• My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, or workflow with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.
• I am targeting the staged branch for this pull request.

---

Description

Adds a new skill that generates narrative-driven commit messages following the Conventional Commits format.
Instead of describing what changed, it tells the story of why — giving teams a richer, more useful git history.
Triggers: "write a commit message", "generate a commit", "describe my changes", "help me commit", "summarize my diff"
Includes a bundled conventional-commits-guide.md reference covering all commit types with real examples.

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• Update to existing instruction, prompt, agent, plugin, skill, or workflow.
• Other (please specify):

---

Additional Notes

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[github-actions]

🔍 Skill Validator Results

✅ All checks passed

Scope	Checked
Skills	1
Agents	1
Total	2
Severity	Count
---	---:
❌ Errors	0
⚠️ Warnings	0
ℹ️ Advisories	0

Summary

Level	Finding
ℹ️	Found 1 skill(s)
ℹ️	[commit-message-storyteller] 📊 commit-message-storyteller: 1,178 BPE tokens [chars/4: 1,289] (detailed ✓), 14 sections, 3 code blocks
ℹ️	✅ All checks passed (1 skill(s))

Full validator output

```text Found 1 skill(s) [commit-message-storyteller] 📊 commit-message-storyteller: 1,178 BPE tokens [chars/4: 1,289] (detailed ✓), 14 sections, 3 code blocks ✅ All checks passed (1 skill(s)) ```

[Copilot]

Pull request overview

Adds a new commit-message-storyteller skill to generate narrative, “why-focused” Conventional Commits messages from diffs or change descriptions, and registers it in the skills index.

Changes:

• Added commit-message-storyteller skill definition (SKILL.md) with guidance and examples.
• Added a bundled Conventional Commits quick reference guide for commit types and patterns.
• Updated docs/README.skills.md to list the new skill.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
skills/commit-message-storyteller/SKILL.md	Introduces the new skill instructions, workflow, and output format.
skills/commit-message-storyteller/conventional-commits-guide.md	Adds a bundled Conventional Commits reference guide used by the skill.
docs/README.skills.md	Registers the new skill in the documentation index.

[Copilot]

references/conventional-commits-guide.md is referenced here, but the bundled guide file is currently located at skills/commit-message-storyteller/conventional-commits-guide.md (no references/ directory). This makes the reference incorrect. Either move the guide into a references/ subfolder or update this path to match the actual file location.

Suggested change

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

[Copilot]

This reference to references/conventional-commits-guide.md doesn’t match the current location of the guide file (skills/commit-message-storyteller/conventional-commits-guide.md). Update the path here as well (or move the guide into references/) to avoid broken pointers in the skill instructions.

Suggested change

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

[aaronpowell]

It looks like you've incorrectly branched from the main branch not staged, and as a result all the materialised plugins are included in this PR.

You can attempt to fix this with a rebase:

git fetch origin staged
git rebase --onto origin/staged origin/main <branch name>
git push --force-with-lease

If that does not resolve it, you can run npm run plugin:clean which will delete the materialised plugins and you can commit that change.

[kwekudzata]

Hi @aaronpowell, I've addressed your feedback — removed the materialised plugins using npm run plugin:clean and pushed the fix. The diff should now only contain the skill files. Happy to make any other changes needed. Thanks!

[aaronpowell]

It still has changes on a number of plugin.json files - sometimes to script isn't able to properly reconcile everything, so you might have to manually undo those changes.

Also, having a look at the skill itself - the file with the conventional commit info should be in a references folder per the spec.

[kwekudzata]

Hi @aaronpowell, both issues are fixed — moved the conventional commits guide into the references/ folder and manually reverted the plugin.json changes. The diff should now be clean. Thanks for the patience!

[aaronpowell]

There's still something messed up in the README's, which is causing a block in the branch updating which would fix the plugin.json diffs

[kwekudzata]

Hi @aaronpowell, fixed the README — reset it to the staged base and regenerated with npm start. The diff should now be clean with only the skill entry added.

[kwekudzata]

@all-contributors please add @kwekudzata for content

[allcontributors]

@kwekudzata

I've put up a pull request to add @kwekudzata! 🎉

[kwekudzata]

Hi @aaronpowell, the all-contributors bot opened this PR targeting main instead of staged — I don't have control over where the bot targets. Could you redirect or merge it manually? Thanks!