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/worktree
development
VerifiedTrustedCommunity
--- name: worktree description: Coordinate multiple agents on one repo via a worktree-lock pool, so two agents never clobber each other's working tree. Acquire the first free slot (main, then beta/gamma… worktrees, created on demand), work there on your own branch, release when you've pushed. Use before modifying any repo that might be in use by another agent (factory, dataforce, etc.), or whenever you're told a repo is being worked on. Backed by `ro worktree`. category: development argument-hin
SKILL.mdUpdated May 25, 2026
RonanCodes/skills/ship
testing
VerifiedTrustedCommunity
--- name: ship description: Ship a feature branch the local-CI-first way — run the full local gate, push, open a PR, squash-merge, then deploy, without waiting on GitHub Actions. Use when a branch is ready for main and you want it merged and deployed now. Reads CI policy from `ro ci` (default skips remote CI because GitHub Actions billing keeps hitting limits). Sibling to /ro:gh-ship (waits on GitHub checks) and /ro:cf-ship (the deploy half). Triggers on "ship it", "ship this", "merge and deploy
SKILL.mdUpdated May 25, 2026
RonanCodes/skills/setup-logging
testing
VerifiedTrustedCommunity
--- name: setup-logging description: Set up (or audit) the observability stack in a TanStack Start + Cloudflare Workers app so it is "diagnosable by default" — structured logging (logtape) with a request context carrying trace_id + userId + tenant/orgId, a trace_id propagated FE→BE→logs→Sentry→PostHog, Cloudflare Workers observability enabled, and Sentry + PostHog wired. Two modes: `setup` (wire it into an app) and `audit` (check an existing app + report gaps). Use when scaffolding a new app, wh
SKILL.mdUpdated May 24, 2026
RonanCodes/env
development
VerifiedTrustedCommunity
Manage credentials INSIDE the active ~/.claude/.env file — read which token/account to use for a given app (Simplicity vs Dataforce vs Ronan-personal), add or update a secret WITHOUT it passing through the chat (an interactive Terminal window prompts for it), and track secrets that were exposed in a transcript so they get rotated. Sibling to /ro:context (which switches WHICH env file is active). Use when the user wants to add an API key/token/secret, asks "which credential do I use for X", needs the env organized/labelled, or a secret was pasted into the chat and should be rotated.
SKILL.mdUpdated May 24, 2026