cantpr09ram/commit
skills/commit/SKILL.md
Read this skill before making git commits
tools
Updated Apr 22, 2026
$ install --global
skillsauthnpx skillsauth add cantpr09ram/agent-staff 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 23, 2026, 12:18 AM141.3s1 file scanned
SKILL.md
- name:
- commit
- description:
- Read this skill before making git commits
Create a git commit for the current changes using a concise Conventional Commits-style subject.
Format
<type>(<scope>): <summary>
typeREQUIRED. Usefeatfor new features,fixfor bug fixes. Other common types:docs,refactor,chore,test,perf.scopeOPTIONAL. Short noun in parentheses for the affected area (e.g.,api,parser,ui).summaryREQUIRED. Short, imperative, <= 72 chars, no trailing period.
Notes
- Body is OPTIONAL. If needed, add a blank line after the subject and write short paragraphs.
- Do NOT include breaking-change markers or footers.
- Do NOT add sign-offs (no
Signed-off-by). - Only commit; do NOT push.
- If it is unclear whether a file should be included, ask the user which files to commit.
- Treat any caller-provided arguments as additional commit guidance. Common patterns:
- Freeform instructions should influence scope, summary, and body.
- File paths or globs should limit which files to commit. If files are specified, only stage/commit those unless the user explicitly asks otherwise.
- If arguments combine files and instructions, honor both.
Steps
- Infer from the prompt if the user provided specific file paths/globs and/or additional instructions.
- Review
git statusandgit diffto understand the current changes (limit to argument-specified files if provided). - (Optional) Run
git log -n 50 --pretty=format:%sto see commonly used scopes. - If there are ambiguous extra files, ask the user for clarification before committing.
- Stage only the intended files (all changes if no files specified).
- Run
git commit -m "<subject>"(and-m "<body>"if needed).
Related Skills
cantpr09ram/value
testing
VerifiedTrustedCommunity
Use abstract principles to evaluate design and engineering decisions.
SKILL.mdUpdated Apr 22, 2026
cantpr09ram/uv
development
VerifiedTrustedCommunity
Use `uv` instead of pip/python/venv. Run scripts with `uv run script.py`, add deps with `uv add`, use inline script metadata for standalone scripts.
SKILL.mdUpdated Apr 22, 2026
cantpr09ram/tmux
tools
VerifiedTrustedCommunity
Remote control tmux sessions for interactive CLIs (python, gdb, etc.) by sending keystrokes and scraping pane output.
SKILL.mdUpdated Apr 22, 2026
cantpr09ram/github
tools
VerifiedTrustedCommunity
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
SKILL.mdUpdated Apr 22, 2026