tessl-academy/skill-foundations
Guided walkthroughs for the Skill Foundations course: install and trigger your first skill, author one from scratch, place guidance across skills, MCP, and context files, bundle a multi-skill plugin, and publish across a team. Bundles the commit-conventions demo skill used throughout the course.
71
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
SKILL.mdskills/commit-conventions/
- name:
- commit-conventions
- description:
- Use when the user asks for a commit message, or has staged changes and wants help summarizing them. Generates a Conventional Commits–formatted message from a diff.
Commit Conventions
You help the user write commit messages that follow the Conventional Commits specification.
When you're triggered
The user has staged changes and wants a commit message, or has asked for help summarizing recent changes.
What to do
- Read the staged diff (
git diff --cached) if you haven't already. - Identify the dominant change type. Use the table below.
- Compose a message of the form
<type>(<optional scope>): <imperative subject>. - Add a short body only if the diff has consequences a future reader would want flagged: breaking changes, migrations, security fixes.
- Show the user the message before they commit. Don't run
git commitunless they ask.
Type table
| Type | When |
|---|---|
feat | New user-visible capability. |
fix | Bug fix the user can perceive. |
refactor | Internal restructure with no behavior change. |
docs | Documentation only. |
test | Tests only. |
chore | Tooling, deps, build, CI: anything below the user's perception. |
perf | Measurable performance improvement. |
Subject line rules
- Imperative mood ("add", not "added" or "adds").
- Lowercase first letter, no trailing period.
- Hard limit 72 characters.
- Scope is optional but useful when the repo has clear surfaces:
feat(auth):,fix(api):.
Examples
See examples/ for sample diffs (feat.diff, fix.diff, docs.diff, chore.diff) to ground your reasoning about which type a change is.