ar4mirez/commit-message
internal/skills/content/commit-message/SKILL.md
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages, reviewing staged changes, or wants to commit with a well-formatted message following conventional commits format.
$ install --global
skillsauthnpx skillsauth add ar4mirez/samuel commit-messageInstall 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 30, 2026, 3:52 AM16.4s1 file scanned
SKILL.md
- name:
- commit-message
- description:
- |
- license:
- MIT
- author:
- samuel
- version:
- 1.0
- category:
- workflow
Commit Message Generator
Purpose
Generate well-formatted commit messages following the Conventional Commits specification.
When to Use
- User asks "help me write a commit message"
- User says "commit this" or "commit my changes"
- User wants to review staged changes before committing
- User asks for commit message suggestions
- User mentions "conventional commit" or asks about commit format
Instructions
-
Check staged changes:
git diff --staged -
If no staged changes, check unstaged:
git diff -
Analyze the changes and identify:
- Type: feat, fix, docs, refactor, test, chore, perf, ci, style, build
- Scope: Affected area/module (optional but recommended)
- Description: What changed and why
-
Generate commit message in format:
type(scope): brief description Optional body with more details. - Bullet points for multiple changes - Explain the "why" not just "what" Optional footer for breaking changes or issue refs.
Commit Types
| Type | Description |
|------|-------------|
| feat | New feature or capability |
| fix | Bug fix |
| docs | Documentation only |
| refactor | Code change that neither fixes nor adds feature |
| test | Adding or updating tests |
| chore | Maintenance, dependencies, configs |
| perf | Performance improvement |
| ci | CI/CD changes |
| style | Formatting, whitespace (no code change) |
| build | Build system or external dependencies |
Examples
Example 1: Feature Addition
Changes: Added new user authentication endpoint
Output:
feat(auth): add user authentication endpoint
- Implement JWT-based authentication
- Add login and logout endpoints
- Include token refresh mechanism
Closes #123
Example 2: Bug Fix
Changes: Fixed date display issue in reports
Output:
fix(reports): correct date formatting in timezone conversion
Use UTC timestamps consistently across report generation.
Previous implementation used local time, causing incorrect
dates for users in different timezones.
Example 3: Refactoring
Changes: Extracted duplicate validation logic
Output:
refactor(validation): extract common validation utilities
- Move email validation to shared utils
- Create reusable phone number validator
- Reduce code duplication across forms
Example 4: Breaking Change
Changes: Changed API response format
Output:
feat(api)!: change response format to JSON:API spec
BREAKING CHANGE: API responses now follow JSON:API specification.
Clients need to update their response parsing logic.
Migration guide: docs/migration-v2.md
Guidelines
- First line: Under 72 characters
- Use imperative mood: "add" not "added", "fix" not "fixed"
- Scope is optional but helps with changelogs
- Body: Explain "why" for non-obvious changes
- Footer: Reference issues, note breaking changes
- Separate concerns: One logical change per commit
Co-Author Attribution
When AI assists with commits, include attribution:
Co-Authored-By: Claude <[email protected]>
Related Skills
ar4mirez/zig-guide
development
VerifiedTrustedCommunity
Zig language guardrails, patterns, and best practices for AI-assisted development. Use when working with Zig files (.zig), build.zig, or when the user mentions Zig. Provides comptime patterns, allocator conventions, C interop guidelines, and testing standards specific to this project's coding standards.
8SKILL.mdUpdated Apr 30, 2026
ar4mirez/wordpress
tools
VerifiedTrustedCommunity
WordPress framework guardrails, patterns, and best practices for AI-assisted development. Use when working with WordPress projects, or when the user mentions WordPress. Provides theme development, plugin architecture, REST API, blocks, and security guidelines.
8SKILL.mdUpdated Apr 30, 2026
ar4mirez/webapp-testing
tools
VerifiedTrustedCommunity
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs. Use when testing web apps, automating browser interactions, or debugging frontend issues.
8SKILL.mdUpdated Apr 30, 2026
ar4mirez/web-artifacts-builder
tools
VerifiedTrustedCommunity
Suite of tools for creating elaborate, multi-component web applications using modern frontend technologies (React, Tailwind CSS, shadcn/ui). Use for complex projects requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX pages.
8SKILL.mdUpdated Apr 30, 2026