kokatsu/commit
.claude/skills/commit/SKILL.md
Create a git commit following Conventional Commits. Use when the user asks to commit changes.
tools
Updated Apr 15, 2026
$ install --global
skillsauthnpx skillsauth add kokatsu/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: Apr 15, 2026, 1:30 PM13.9s1 file scanned
SKILL.md
- name:
- commit
- description:
- Create a git commit following Conventional Commits. Use when the user asks to commit changes.
Commit Skill
Create a git commit following Conventional Commits (@commitlint/config-conventional).
Usage
/commit
Workflow
- Run
git statusandgit diff --stagedto understand changes - If there are unstaged changes, ask the user before proceeding
- Generate an appropriate commit message based on the staged changes
- Present the generated commit message to the user and wait for approval
- Execute the commit
Commit Convention
Follow Conventional Commits (@commitlint/config-conventional).
Project-specific guidelines:
- Config file tweaks (e.g. renovate.json5, flake.nix settings) →
chore, notfeat - Adding a new overlay or tool →
feat - Dependency version bumps →
build(deps)
Critical Rules
- Only commit staged changes — never
git addunstaged changes without explicit permission - Commit messages must be in English — both subject and body
- Use HEREDOC format to pass messages — avoids shell escaping issues
- Never use
--no-verify— if a hook fails, investigate and fix the root cause - Always get user approval before committing — present the message and do not commit without confirmation
- Only amend when the user explicitly requests it
Related Skills
kokatsu/ux-psychology
development
VerifiedTrustedCommunity
Apply UX psychology principles when building UI components, forms, pricing pages, onboarding flows, checkout experiences, modals, or any user-facing interface. Use when designing CTAs, implementing progress indicators, creating loading states, improving user engagement, or reviewing UI for psychological effectiveness.
SKILL.mdUpdated Apr 15, 2026
kokatsu/tdd
development
VerifiedTrustedCommunity
Guide TDD workflow with Red-Green-Refactor cycle. Use when the user asks to "write tests first", "TDD", "test-driven", "テスト駆動", "TDDで実装", "テストファースト".
SKILL.mdUpdated Apr 15, 2026
kokatsu/research
development
VerifiedTrustedCommunity
Deep-read a codebase area and write findings to research.md. Use for thorough investigation before planning.
SKILL.mdUpdated Apr 15, 2026
kokatsu/plan
development
VerifiedTrustedCommunity
Create a detailed implementation plan in plan.md. Never implements code. Use after /research or when planning a feature.
SKILL.mdUpdated Apr 15, 2026