ReddRadar
Agent skill
semantic-commit
Generate semantic commit messages from staged changes. Use when committing code to produce consistent, well-structured commit messages following conventional commit format.
Install this agent skill to your Project
npx add-skill https://github.com/jonmagic/skills/tree/main/skills/semantic-commit
SKILL.md
Semantic Commit
Generate commit messages following the conventional commit format: <type>(<scope>): <subject>
Format
<type>(<scope>): <subject>
<body>
- type: Required. Category of change.
- scope: Optional. Omit if unclear or not valuable.
- subject: Present tense, no period, under 72 chars.
- body: Optional. Explain what/why, not how. Wrap at 72 chars.
Types
| Type | Use for |
|---|---|
feat |
New user-facing feature |
fix |
Bug fix |
docs |
Documentation only |
style |
Formatting, whitespace (no logic change) |
refactor |
Code change that doesn't fix or add |
test |
Adding or updating tests |
chore |
Build, CI, dependencies |
Rules
- Subject line under 72 characters
- Present tense ("add" not "added")
- No period at end of subject
- Blank line between subject and body
- Body explains what/why, wrapped at 72 chars
- Single-line OK for trivial changes
- Non-trivial changes should include body
Examples
Trivial:
docs: fix typo in readme
Simple with scope:
feat(auth): add password reset flow
With body:
fix(api): handle empty response from upstream
Add null check before parsing response body. Previously, empty
responses from the payments service caused JSON parse errors.
Workflow
- Review staged changes with
git diff --cached - Identify the primary type and optional scope
- Write subject summarizing the change
- Add body for non-trivial changes explaining what/why
- Commit using HEREDOC format for proper formatting
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
jonmagic/skills
markdown-to-standalone-html
Convert Markdown documents (*.md files) to self-contained HTML files with embedded images. Use when you need a portable, offline-friendly single HTML file from Markdown—ideal for blog posts, essays, reports, or any content that should work without external dependencies.
jonmagic/skills
brain-operating-system
Quick reference for operating within jonmagic's second-brain workspace. Use when working with files in the brain repository—provides directory structure, naming conventions, append-only norms, wikilink patterns, frontmatter requirements, project conventions, and file organization rules. Essential for understanding where to create files, how to name them, and how to maintain continuity with existing structures.
jonmagic/skills
archive-meeting
Archive one or more meetings into the brain repo by importing Zoom transcript folders (~/Documents/Zoom/*) and/or downloaded Teams .vtt files (~/Downloads/*.vtt), then generating a transcript markdown file, an executive summary, and creating meeting notes. Use when the user says "archive meeting", "archive my last meeting", "process these transcripts", or similar.
jonmagic/skills
brain-commit
Analyze changes in the Brain repo and create semantic commits. Use when the user wants to commit their brain changes with meaningful, organized commit messages. Analyzes staged/unstaged changes, groups related files, creates appropriate commits, and pushes without user interaction.
jonmagic/skills
session-to-brain
Archive a Copilot CLI session to the brain. Creates a daily project file with the session transcript and adds a resume link to the weekly note. Use when ending a significant work session to preserve context for future reference.
jonmagic/skills
create-bookmark
Save a URL as a bookmark with frontmatter and a blurb or AI summary. Use when the user says "bookmark this", "save this link", or shares a URL they want to remember.
Didn't find tool you were looking for?