not-matthias/commit
modules/home/programs/cli-agents/shared/skills/coding/commit/SKILL.md
Read this skill before making git commits
$ install --global
skillsauthnpx skillsauth add not-matthias/dotfiles-nix 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 7, 2026, 6:02 AM34.8s1 file scanned
SKILL.md
- name:
- commit
- description:
- Read this skill before making git commits
<!-- Source: https://github.com/mitsuhiko/agent-stuff/blob/main/skills/commit/SKILL.md -->
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 strongly encouraged — always include one unless the change is trivially obvious (e.g., fixing a typo). The body should explain what changed, why it changed, the approach taken, and any notable decisions. A reader of
git logshould understand the change without looking at the diff. - 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.
Examples
Good commit messages are specific about why the change matters, not just what changed:
fix: keep keyboards and mice awake despite powertop autosuspend
fix(ida-pro): fix plugin loading errors for bindiff and binsync
fix: pin docker container images to specific versions instead of latest
fix: tune ZFS txg_sync and zrepl retention to reduce CPU overhead
feat: add agent-browser with versioned npm cache and corruption recovery
feat(niri): add shortcuts for focusing on columns
Bad — vague, just restates the diff
feat: update config
fix: fix bug
feat: add pi-mono Nix package with extension system
chore: update flake
fix: soulsync stuff
Context
- Working tree status: !
git status --short - Staged diff: !
git diff --cached - Unstaged diff: !
git diff - Recent commit style: !
git log -n 20 --pretty=format:%s
Steps
- Infer from the prompt if the user provided specific file paths/globs and/or additional instructions.
- Review the embedded context above to understand the current changes (limit to argument-specified files if provided).
- 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
not-matthias/personal-notes
documentation
VerifiedTrustedCommunity
Save notes, journal entries, and research to the personal-notes Obsidian vault (personal-vault-v2). Use when the user asks to 'save note', 'save to notes', 'write to personal notes', 'save to daily notes', 'note this down', or wants to persist findings/analysis to their personal vault.
9SKILL.mdUpdated Jul 29, 2026
not-matthias/fix-pr
documentation
VerifiedTrustedCommunity
Use whenever the user asks to address, fix, resolve, review, or respond to pull-request comments or review feedback.
9SKILL.mdUpdated Jul 29, 2026
not-matthias/code-style
development
VerifiedTrustedCommunity
Apply Not Matthias's Rust-first personal coding style. Use whenever the user explicitly asks to apply or review their code style, make Rust match their preferences, perform a style pass, or simplify/refactor according to their conventions. Inspect only task-touched code, honor local project conventions first, and make only safe opt-out style edits.
9SKILL.mdUpdated Jul 29, 2026
not-matthias/ast-grep
development
VerifiedTrustedCommunity
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for code patterns, find specific language constructs, or locate code with particular structural characteristics.
9SKILL.mdUpdated Jul 29, 2026