cuozg/git-commit
skills/git-commit/SKILL.md
Use this skill to stage and commit changes with a clean, imperative-mood commit message. Use it whenever the user wants to save their work, says "commit this," "save my changes," or "commit what I've done." Handles both staged and unstaged files, writes structured messages with bullet points for multi-change commits. Never pushes to remote. Do not use for amending — use git-comment for that.
$ install --global
skillsauthnpx skillsauth add cuozg/oh-my-skills git-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, 1:02 PM133.8s1 file scanned
SKILL.md
- name:
- git-commit
- description:
- >
- author:
- kuozg
- version:
- 1.0
git-commit
Stage and commit changes with a clean, imperative-mood commit message. Never pushes to remote.
When to Use
- Saving completed work as a logical commit
- Committing a set of related changes with a meaningful message
- Finalizing a bug fix, feature, or refactor into version history
Workflow
- Inspect — Run
git statusandgit diffto understand what has changed - Stage — Run
git addfor relevant files (orgit add -Aif all changes belong together) - Draft — Write an imperative-mood summary line (max 72 chars); add bullet points for multi-change commits
- Commit — Run
git commit -m "{message}"with the drafted message - Confirm — Run
git statusto verify the working tree is clean
Rules
- Use imperative mood: "Add", "Fix", "Refactor" — not "Added" or "Adding"
- Keep summary line under 72 characters
- Use bullet points in the body when multiple distinct changes are present
- Include no AI-generated metadata, co-author tags, or tool signatures
- Never run
git push— local commit only - Never amend a commit that has already been pushed
Output Format
A single local commit with a clean message. No remote changes. git status shows a clean working tree.
Related Skills
cuozg/unity-image-gen
tools
VerifiedTrustedCommunity
Generate Unity raster image assets through Unity MCP: game sprites, item art, backgrounds, UI icons, portraits, concept images, transparent cutouts, image edits, upscales, background removal, and Unity scene or Game View screenshots. Use when a Unity project needs image files imported under Assets or screenshots captured from the editor. Do not use for meshes, audio, animation, materials, gameplay code, UI Toolkit layout, or generic non-Unity image generation.
4SKILL.mdUpdated May 29, 2026
cuozg/unity-technical
tools
VerifiedTrustedCommunity
Create Unity technical solution documents from user requirements, feature ideas, bug goals, specs, or codebase problems. Use when the user asks for a technical approach, architecture, implementation strategy, solution options, feasibility analysis, system design, or "how should we build/fix this" for Unity runtime, Editor, tools, assets, data, UI, WebGL, SDKs, or production pipelines.
4SKILL.mdUpdated May 26, 2026
cuozg/unity-mcp-orchestrator
tools
VerifiedTrustedCommunity
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
4SKILL.mdUpdated May 21, 2026
cuozg/goal-todo
development
VerifiedTrustedCommunity
Convert a spec document into an implementation TODO list in the same spec folder. U se when the user says goal-todo, todo from spec, generate tasks from spec, turn this spec into todos, create implementation checklist, extract tasks, or asks to read a Docs/Specs design doc and produce what must be implemented. Includes UI/UX review and codebase investigation before writing the checklist. Do not use for implementing the tasks, creating new goal files, writing test cases, or verifying completed work.
4SKILL.mdUpdated May 21, 2026