RonanCodes/commit
skills/commit/SKILL.md
Create git commits with emoji conventional commit format. Handles staging, message formatting, and timestamp rules. Use when committing changes.
development
Updated May 24, 2026
$ install --global
skillsauthnpx skillsauth add RonanCodes/ronan-skills commitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 24, 2026, 2:10 AM41.3s1 file scanned
SKILL.md
- name:
- commit
- description:
- Create git commits with emoji conventional commit format. Handles staging, message formatting, and timestamp rules. Use when committing changes.
- category:
- development
Commit
Create well-formatted git commits with emoji conventional commit style.
Usage
/commit
/commit --amend
Format
Every commit message MUST use this format:
<emoji> <type>: <description>
Single line. Lowercase description. No period at the end. Focus on the "why" not the "what".
Emoji Map
| Emoji | Type | When to use | |-------|------|-------------| | ✨ | feat | New feature or capability | | 🐛 | fix | Bug fix | | 🧪 | test | Adding or fixing tests | | 📝 | docs | Documentation changes | | 🧹 | chore | Maintenance, config, tooling | | ♻️ | refactor | Code restructuring without behaviour change | | 🚀 | deploy | Deployment-related changes | | 🔧 | config | Configuration changes | | ⚡ | perf | Performance improvements | | 🔒 | security | Security fixes |
Examples
✨ feat: add vault search with fuzzy matching
🐛 fix: prevent duplicate wiki pages on re-ingest
♻️ refactor: extract frontmatter parser into shared util
📝 docs: add obsidian integration guide
🧹 chore: update dependencies and clean unused imports
Rules
- Do NOT include
Co-Authored-Bylines - Do NOT add scope in parentheses — use
✨ feat: thingnot✨ feat(scope): thing - Use the emoji that best matches the primary intent of the change
- If a commit spans multiple types, use the most significant one
- Keep the description under 72 characters. This is not just style: repos with a
commitlintcommit-msghook enforceheader-max-length(default 100), and the whole subject line counts, including the leading emoji +type:prefix (about 8-12 chars). A long subject is rejected withheader must not be longer than 100 charactersand the commit never lands. Under 72 keeps you safely inside it. Put detail in the body, not the subject. - Use imperative mood: "add" not "added", "fix" not "fixed"
Workflow
- Run
git statusandgit diffto understand what changed - Run
git log --oneline -5to see recent commit style - Stage the relevant files (prefer specific files over
git add -A) - Draft the commit message following the format above
- Check if there are timestamp rules in the project's CLAUDE.md — if so, apply
GIT_AUTHOR_DATEandGIT_COMMITTER_DATE - Commit and verify with
git status
Passing --amend
If the user passes --amend, amend the previous commit instead of creating a new one. Preserve the original timestamp unless the user specifies otherwise.
Related Skills
RonanCodes/skills/linear-pipeline
testing
VerifiedTrustedCommunity
--- name: linear-pipeline description: The Fable orchestrator for a single dispatched Linear ticket. Holds almost no context itself; it receives `--issue <ID> --detached`, decides the stage sequence, and fans out a sub-agent per stage, passing forward only each stage's artifact (never re-derived, never inlined into its own context). Step zero, before any planning or stage routing, is a boundary triage against `canon/security-boundary.md` (#199): a match tags Ronan Connolly and stops the run, no
SKILL.mdUpdated Jul 5, 2026
RonanCodes/skills/in-your-face
development
VerifiedTrustedCommunity
--- name: in-your-face description: Capture a chat-only answer into a durable artifact (markdown + HTML, PDF when cheap) and launch it automatically so the user cannot miss it. Use when user says "in your face", "don't let me lose this", "save that answer", "make that durable", or right after answering a substantive side question (a recipe, comparison, how-to, or generated prompt) that would otherwise die with the context. category: workflow argument-hint: [--no-open] [--vault <short>] [hint of
SKILL.mdUpdated Jul 5, 2026
RonanCodes/codex
tools
VerifiedTrustedCommunity
One-shot headless OpenAI Codex CLI calls for background/admin AI tasks — summaries, classification, extraction, admin glue. The default engine for anything that runs AI constantly in the background (daemon-driven, per-event), because it bills the flat ChatGPT subscription instead of Claude usage or per-token API spend, and it keeps working while Claude is rate-limited. NEVER for coding — coding stays Claude. Use when a skill or daemon needs a cheap always-on AI call, when the user says "use codex", "ask codex", "codex as backup", or when building a background summarizer/classifier into a listener or loop. Reads auth from ~/.codex/auth.json (ChatGPT account, no API key).
SKILL.mdUpdated Jul 5, 2026
RonanCodes/warranty-check
research
VerifiedTrustedCommunity
Turn a warranty rejection, repair quote, or RMA email into a cited decision brief — legal read (NL/EU consumer law), is the part user-serviceable, live part and new-unit prices, repair-vs-DIY-vs-new economics, before-you-send-it checklist, deadlines. Use when the user pastes or screenshots a repair quote, warranty rejection, "not covered" email, onderzoekskosten fee, or asks "should I repair or replace this".
SKILL.mdUpdated Jul 4, 2026