eddowding/commit
vault/Operations/Claude/skills/coding/commit/SKILL.md
Batch changes into logical commits with proper messages and safe concurrent handling.
tools
Updated Apr 4, 2026
$ install --global
skillsauthnpx skillsauth add eddowding/cortex 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: Apr 4, 2026, 6:39 PM226.7s1 file scanned
SKILL.md
- name:
- commit
- description:
- Batch changes into logical commits with proper messages and safe concurrent handling.
- last_updated:
- 2026-01-10
- tools_required:
- [Bash]
- agent_type:
- main_agent
Git Commit
Batch changes into logical commits following best practices.
[GOAL]
Review git diff, batch changes into logical commits, and commit them safely one at a time.
[CONTEXT]
May be run alongside other agents changing code. Prioritizes data safety and atomic operations.
[PROCESS]
1. Review changes
- Run
git statusandgit diffto understand all changes - List all modified files before proceeding
2. Plan batches
- Each commit = small/medium feature, stage, or cluster of related changes
- Code and docs for same feature go together
- Codebase should be working after each commit
- Don't mix unrelated changes
- If in a conversation: Only commit changes relevant to this conversation
- Prefer older files first (less likely another agent is working on them)
3. Commit each batch atomically
- ALWAYS chain reset/add/commit to avoid interference:
git reset HEAD unwanted-file && git add "wanted-file" && git commit -m "type: subject" - ALWAYS quote paths (especially SvelteKit routes with brackets)
4. Format commit message
<type>: <subject> (50 chars max)
<body> (optional, wrap at 72 chars)
- Planning doc: yyMMddx_feature_name.md (if applicable)
- Bullet points for multiple changes
Types: feat, fix, docs, style, refactor, test, chore
[IMPORTANT]
- Never do anything destructive without explicit user instruction
- Quote file paths:
git add "path/with/[brackets]/file.ts" - Chain operations: reset && add && commit (atomic)
- Stop immediately on merge conflicts or unexpected issues
- Check .gitignore: If you notice uncommittable files (node_modules, secrets), ask user
- Parallel agents: Provide context to help write good commit messages
[FALLBACK]
If codebase is in partial/broken state, prioritize commits that leave it working.
When in doubt, ask user before proceeding.
Related Skills
eddowding/when-stuck
tools
VerifiedTrustedCommunity
Dispatch to the right problem-solving technique based on how you're stuck.
SKILL.mdUpdated Apr 4, 2026
eddowding/sounding-board-mode
testing
VerifiedTrustedCommunity
Interactive brainstorming and advisory mode that helps think through questions, critique approaches, propose alternatives, and reach optimal decisions.
SKILL.mdUpdated Apr 4, 2026
eddowding/simplification-cascades
tools
VerifiedTrustedCommunity
Find one insight that eliminates multiple components - 'if this is true, we don't need X, Y, or Z'
SKILL.mdUpdated Apr 4, 2026
eddowding/scale-game
testing
VerifiedTrustedCommunity
Test at extremes (1000x bigger/smaller) to expose fundamental truths hidden at normal scales.
SKILL.mdUpdated Apr 4, 2026