iainmcl/commit-code
claude/skills/commit-code/SKILL.md
Instructions for committing code changes. Use when committing code, creating commits, or pushing changes upstream.
development
Updated May 1, 2026
$ install --global
skillsauthnpx skillsauth add iainmcl/dotfiles commit-codeInstall 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 1, 2026, 9:55 AM117.6s1 file scanned
SKILL.md
- name:
- commit-code
- description:
- Instructions for committing code changes. Use when committing code, creating commits, or pushing changes upstream.
Committing Code Changes
Pre-commit Hooks
Pre-commit hooks will run and may modify files. If hooks modify files:
- Stage the modified files
- Commit again
Commit Message Format
<Title>
<Description>
How to commit
Write the message to a temp file to avoid command substitution prompts:
- Use the
Writetool to write the commit message to/tmp/commit_msg.txt - Then run:
git commit -F /tmp/commit_msg.txt
Never use git commit -m "$(cat <<'EOF' ... EOF)" — the $() substitution triggers a security confirmation prompt.
Rules
Title (first line):
- Keep it brief and descriptive
- Do NOT use semantic commit prefixes (no
feat:,fix:,chore:, etc.)
Description:
- 1-2 sentences maximum - keep it high-level
- Focus on why the change was made, not a granular list of what changed
- The diff already shows the details - don't repeat them in prose
- Do NOT write:
- Bullet lists of every file or function changed
- Vague fluff like "make more resilient", "make more scalable", "handles gracefully"
- Line-by-line summaries of the code changes
Pushing Changes
When changes have been committed ask if we are ready to push. If we are ready to push, push using:
git push origin <branch-name>
If pushing as part of a rebase use
git push --force-with-lease
- Only push upstream when explicitly asked
- The upstream remote is
origin - Never force push - the only exception is when rebasing the branch
Related Skills
iainmcl/weekly-review
development
VerifiedTrustedCommunity
Run a weekly achievement review - pulls from Jira, GitHub, and Slack to capture what you shipped in the last week, maps achievements to your 2026 goals, and appends impact-focused entries to your brag doc. Use when asked to "do a weekly review", "capture this week's wins", "update my brag doc", "what did I ship this week", "record my achievements", "what have I done this week", "add to my performance doc", or anything about tracking weekly progress, brag doc entries, or performance evidence. Trigger even if the user just says "weekly review" or "document what I did".
SKILL.mdUpdated May 19, 2026
iainmcl/skill-creator
testing
VerifiedTrustedCommunity
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
SKILL.mdUpdated May 19, 2026
iainmcl/setup-project-update
tools
VerifiedTrustedCommunity
Set up a project update config for the current repo, so that running project-update requires no setup questions. Use when asked to "set up project updates", "configure project update", "initialise project update", or "create a project update config". Run this once per project repo.
SKILL.mdUpdated May 19, 2026
iainmcl/sentry-fix
testing
VerifiedTrustedCommunity
Find the highest-frequency unresolved Sentry error for the VAT & Invoicing or Billing team, understand its root cause, create a Jira ticket in the APP project, implement a fix, and open a draft PR. Use when asked to "fix sentry issues", "triage sentry errors", "look at sentry", "what's broken in sentry", "create a fix for a sentry issue", or "sentry triage". Runs the full flow autonomously in the background.
SKILL.mdUpdated May 19, 2026