techdufus/commit
roles/omp/files/skills/commit/SKILL.md
Preparing and creating git commits when explicitly requested; covers staged diff review, secrets checks, and conventional commit messages.
$ install --global
skillsauthnpx skillsauth add techdufus/dotfiles 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: Jun 5, 2026, 4:58 AM49.3s1 file scanned
SKILL.md
- name:
- commit
- description:
- Preparing and creating git commits when explicitly requested; covers staged diff review, secrets checks, and conventional commit messages.
- condition:
- User explicitly asks to commit, ship, wrap up with a commit, or create a commit message.
Commit playbook
Only use this skill when the user explicitly requests a commit or commit message.
Procedure
- Inspect current git status and diff before staging or committing.
- Do not revert, stash, or overwrite unexpected user changes.
- Check staged and unstaged diffs for secrets, credentials, tokens, private keys, and plaintext secret material.
- Stage only files relevant to the requested change.
- Generate a concise conventional commit message from the staged diff.
- Commit only after verification has run or the user explicitly accepts the remaining risk.
Message shape
- Use conventional commit format:
type(scope): summary. - Prefer
fix,feat,refactor,docs,test,chore, orci. - Summary should describe user-visible or maintainer-visible effect, not implementation trivia.
PR follow-ups
- For follow-up work on an open PR, prefer creating a new commit and pushing normally so review history remains chronological.
- Do not amend, rebase, squash, or force-push an existing PR branch unless the user explicitly asks to rewrite history.
- If history rewriting is explicitly requested, use
--force-with-lease, explain why it is needed, and never use plain--force.
Hard stops
- Do not commit secrets.
- Do not commit unrelated changes without explicit user approval.
- Do not claim verification that was not run.
Related Skills
techdufus/verification
testing
VerifiedTrustedCommunity
Verifying implementation work before claiming completion; covers tests, affected artifacts, evidence, and unresolved risks.
402SKILL.mdUpdated May 20, 2026
techdufus/semantic-compression
testing
VerifiedTrustedCommunity
Aggressively remove grammatical scaffolding LLMs reconstruct while preserving meaning-carrying content. Output may be fragments. Use when compressing text for prompts, reducing token count, preparing context for LLM input, or making documentation more token-efficient. Applies LLM-aware compression rules that delete predictable grammar while preserving semantics.
402SKILL.mdUpdated May 20, 2026
techdufus/work
testing
VerifiedTrustedCommunity
Use when the user explicitly invokes $work or asks for execution strategy for complex engineering work with unclear scope, dependent steps, or separable workstreams.
402SKILL.mdUpdated Apr 25, 2026
techdufus/intent
testing
VerifiedTrustedCommunity
Extract the underlying intent behind a request, issue, PR, or diff. Focus on problem and desired outcome; do not propose implementation, testing strategy, or rollout plans.
402SKILL.mdUpdated Apr 25, 2026