popoffvg/work-commit
skills/work-commit/SKILL.md
Git commit message conventions. Used during implement phase when committing after each completed TODO.
$ install --global
skillsauthnpx skillsauth add popoffvg/dotfiles work-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 16, 2026, 2:26 AM7.1s1 file scanned
SKILL.md
- name:
- work-commit
- description:
- >
Commit Message Rules
Format
<prefix>: <why this change exists>
Prefixes
| Prefix | When |
|--------|------|
| feat | New functionality, new behavior |
| fix | Bug fix — describe the bug, not the fix |
| doc | Documentation changes only |
| test | Adding or updating tests only |
| build | Build system, CI, dependencies |
| refactor | Code restructuring without behavior change |
Message Content
The message describes why, not what.
-
❌
feat: add handleRefresh function— describes what was added -
✅
feat: support token refresh on expired sessions— describes why -
❌
fix: check for nil pointer in handler— describes the fix -
✅
fix: crash when auth token is missing from request— describes the bug -
❌
refactor: move code to utils— describes what -
✅
refactor: isolate auth logic for reuse across endpoints— describes the goal
Rules
- One prefix per commit
- Message ≤ 72 characters
- Imperative mood: "support", not "supports" or "supported"
- No period at the end
- No ticket/issue numbers unless they add clarity
- If a commit touches tests AND code, use the prefix for the code change (e.g.
feat), nottest
Granularity
Each TODO = one commit. Exception: if the user explicitly says "join", "merge", or "squash" multiple TODOs, combine them into one commit with a unified message covering all of them.
When squashing N commits on request:
git reset --soft HEAD~N
git commit -m "<prefix>: <unified why covering all N changes>"
The unified message must cover the full scope — do not just repeat the first TODO's message.
Autoresearch rules
Eval checklist:
- Does the commit message start with a valid prefix (feat|fix|doc|test|build|refactor)?
- Does the message describe WHY the change exists, not WHAT was changed?
- Is the message ≤72 chars, imperative mood, no trailing period?
- Is the prefix correct for the change type (not using
featfor a bug fix)?
Test inputs:
- "Commit adding a new API endpoint with tests"
- "Commit fixing a nil pointer dereference"
- "Commit refactoring a function into smaller pieces with no behavior change"
Can change: prefix list, message examples, formatting rules Cannot change: imperative mood requirement, why-not-what principle, 72-char limit Min sessions before eval: 5 Runs per experiment: 3
Related Skills
popoffvg/improve-claude-local
tools
VerifiedTrustedCommunity
Improve a whole CLAUDE.local.md — the private, per-project rules captured from user corrections. Wraps each conditional rule in a <task-relevant> block so it only surfaces for matching work, merges duplicates, generalizes one-off facts, drops stale entries, and routes raw project facts to engram. Use when the user says "improve claude.local", "clean up the local rules", "claude.local is bloated", or after the Stop hook has appended many rules.
2SKILL.mdUpdated Jun 25, 2026
popoffvg/workflow
testing
VerifiedTrustedCommunity
WM pipeline and conventions shared across all phases. Agents must read this before spec, impl, or verify work.
2SKILL.mdUpdated Jun 19, 2026
popoffvg/code
development
VerifiedTrustedCommunity
One entry point for spec writing, implementation, and bug fixing. Default is new (write spec → grill loop → produce notes → author TODO bodies). Other subcommands: verify (audit), revise (sync to shipped), prototype (settle a decision), code-map (diagram), impl (execute one TODO), fix (analyze cause, correct thoughts, fix behavior), help (this page). Invoke as /code <subcommand>.
2SKILL.mdUpdated Jun 19, 2026
popoffvg/red-green-refactor
development
VerifiedTrustedCommunity
Red-Green-Refactor cycle for bug fixes. Before fixing a bug, first write a failing test that reproduces it (Red), then make the minimal change to pass (Green), then clean up the code (Refactor). Use on any bug fix, error correction, failing test repair, or when user says "fix this bug".
2SKILL.mdUpdated Jun 18, 2026