cuozg/git-comment
skills/git-comment/SKILL.md
Use this skill to rewrite the most recent local commit message to be clean, imperative, and well-structured. Use it when the last commit message is unclear, auto-generated, or the user says "fix my commit message," "that commit message is bad," or "reword the last commit." Never touches pushed commits. Do not use for making new commits — use git-commit for that.
$ install --global
skillsauthnpx skillsauth add cuozg/oh-my-skills git-commentInstall 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 PM167.7s1 file scanned
SKILL.md
- name:
- git-comment
- description:
- >
- author:
- kuozg
- version:
- 1.0
git-comment
Rewrite the most recent local commit message to be clear, imperative, and well-structured. Never touches pushed commits.
When to Use
- The last commit message is unclear, verbose, or auto-generated
- A commit message needs bullet points added for multi-change clarity
- Fixing a typo or wrong scope in the commit summary
- Cleaning up before creating a PR
Workflow
- Check — Run
git log -1to read the current message andgit statusto confirm no unpushed remotes have the commit - Verify — Run
git log --oneline origin/HEAD..HEAD(or equivalent) to confirm the commit is local only - Draft — Write the improved message: imperative summary line + optional bullet body
- Amend — Run
git commit --amend -m "{new message}"(or open editor if body needed) - Confirm — Run
git log -1to verify the updated message
Rules
- Never amend if the commit has already been pushed to any remote branch
- Use imperative mood: "Fix", "Add", "Update" — not past tense
- Keep summary under 72 characters
- Add bullet points in the body for commits touching multiple concerns
- Include no AI metadata or tool signatures in the message
Output Format
Amended local commit with an improved message. No remote changes. git log -1 shows the updated message.
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