jim60105/commit
skills/commit/SKILL.md
Create a git commit with clear, conventional commit messages. You MUST read this when the user wants to commit staged changes, write a commit message, or finalize code changes with proper conventional commit format since it describes how to follow the user's specific requirements.
$ install --global
skillsauthnpx skillsauth add jim60105/copilot-prompt 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 26, 2026, 7:44 AM20.1s1 file scanned
SKILL.md
- name:
- commit
- description:
- Create a git commit with clear, conventional commit messages. You MUST read this when the user wants to commit staged changes, write a commit message, or finalize code changes with proper conventional commit format since it describes how to follow the user's specific requirements.
- license:
- GFDL-1.3-or-later
- author:
- [email protected]
Commit
Create git commits with conventional commit messages.
Steps
- Run
git --no-pager diffto review the full changes. - Analyze the changes thoroughly to understand what was modified.
- Create a git commit with a clear, conventional commit message.
Commit Guidelines
Format
- Title: Use conventional commit format (
type: description) - Body: Include brief description linking to the issue
- Language: Always write commits in English
- Newline: Use real newlines in commit message, not
\n - Resolve Issues: If applicable, include "Resolves issue #X" in the body to link the commit to an issue. Skip this if there is no relevant issue.
IMPORTANT: Don't use \n that's not working, use real newlines!!!
IMPORTANT: Don't use \n that's not working, use real newlines!!!
IMPORTANT: Don't use \n that's not working, use real newlines!!!
Commit Command Template
git commit -m "chore: standardize linting, centralize guides, pin Python
- Introduce a root .flake8 config enforcing a 100-character line limit and ignoring specific style checks
- Remove inlined Python and Zsh guideline sections from copilot-instructions.md in favor of dedicated files
- Pin project Python version to 3.12 via a new .python-version file
- Rename docs/testing-guideline.md to docs/zsh-testing-guideline.md
- Refactor fetch_tags.py for consistent double-quoted strings, streamlined pattern definitions, logging calls, and URL assignment
Resolves issue #42"
Related Skills
jim60105/image-generator-sd-webui
development
VerifiedTrustedCommunity
Generate images via the Stable Diffusion WebUI / Forge HTTP API (AUTOMATIC1111-compatible `/sdapi/v1/*`). Use when the user wants to (1) discover or pick a model / extra module (TE/VAE) / sampler / scheduler / style preset from a running sd-webui server, (2) generate an image with a given prompt (txt2img), (3) check generation progress, (4) cancel/interrupt an in-flight generation, (5) inspect or change a global sd-webui option (e.g. active checkpoint), or (6) test connectivity. This skill talks to a *generic* sd-webui-compatible server (AUTOMATIC1111, Forge, reForge, sd-webui-forge-classic). Do NOT trigger for requests that are purely writing the prompt itself.
21SKILL.mdUpdated May 23, 2026
jim60105/openspec-verify-change
testing
VerifiedTrustedCommunity
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
20SKILL.mdUpdated Jul 20, 2026
jim60105/openspec-update-change
development
VerifiedTrustedCommunity
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
20SKILL.mdUpdated Jul 20, 2026
jim60105/openspec-sync-specs
data-ai
VerifiedTrustedCommunity
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
20SKILL.mdUpdated Jul 20, 2026