SebastienElet/commits
.cursor/skills/commits/SKILL.md
Git commit message conventions (Conventional Commits). Use when writing or reviewing commit messages.
$ install --global
skillsauthnpx skillsauth add SebastienElet/dotfiles commitsInstall 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, 7:18 PM17.2s1 file scanned
SKILL.md
- name:
- commits
- description:
- Git commit message conventions (Conventional Commits). Use when writing or reviewing commit messages.
Commit Message Conventions
Follow the Conventional Commits specification.
Format
<type>(<scope>): <subject>
<body>
<footer>
Types
fix:- Bug fixesrefactor:- Code refactoring (removing code, restructuring without changing behavior)chore:- Maintenance tasks (updates, configuration changes, tooling)feat:- New featuresdocs:- Documentation changesstyle:- Code style changes (formatting, whitespace)test:- Adding or updating testsperf:- Performance improvements
Scope (optional)
Use scope to indicate the area affected:
fish- Fish shell configurationnvim- Neovim configurationcursor- Cursor editor configurationmakefile- Makefile changesscripts- Shell scripts
Examples
refactor: remove opencommit from Makefile
fix(fish): fix arrow for previous/next command
chore: upgrade nvim plugins
refactor(nvim): setup new colorscheme
chore: add cursor rules
Guidelines
- Use lowercase for the subject line
- No period at the end of the subject line
- Use imperative mood ("remove" not "removed" or "removes")
- Keep subject line under 72 characters when possible
- Body and footer are optional for simple changes
Related Skills
SebastienElet/scripts
tools
VerifiedTrustedCommunity
Bash scripts conventions
13SKILL.mdUpdated Apr 16, 2026
SebastienElet/neovim
tools
VerifiedTrustedCommunity
Neovim LazyVim configuration conventions
13SKILL.mdUpdated Apr 16, 2026
SebastienElet/makefile
tools
VerifiedTrustedCommunity
Makefile structure and install workflow
13SKILL.mdUpdated Apr 16, 2026
SebastienElet/johnny-decimal
testing
VerifiedTrustedCommunity
Johnny Decimal + PARA organization
13SKILL.mdUpdated Apr 16, 2026