milanhorvatovic/commit-conventions
.agents/skills/commit-conventions/SKILL.md
Enforces commit message format and conventions for the Skill System Foundry repository. Triggers when composing a commit message, reviewing commit history, squashing commits, or deciding how to describe a change. Also triggers on phrases like "write a commit message," "what should the commit say," "commit message format," or "how to reference an issue in a commit." Use this skill whenever a commit message needs to be written or reviewed.
$ install --global
skillsauthnpx skillsauth add milanhorvatovic/skill-system-foundry commit-conventionsInstall 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, 12:58 PM4.5s1 file scanned
SKILL.md
- name:
- commit-conventions
- description:
- >
Commit Conventions Skill
Enforces commit message format and conventions for the Skill System Foundry repository.
Format
Every commit message starts with a short summary line describing what changed. Use one of these verb prefixes:
| Verb | When to Use | Example |
|---|---|---|
| Update | Enhancement to an existing feature or file | Update validation to check forward slashes |
| Add | Wholly new feature, file, or component | Add critique skill to .agents/ |
| Fix | Bug fix or correction | Fix false positive in name validation |
Rules
- One logical change per commit. Do not mix unrelated changes in a single commit
- Summary line only. Keep it to one line. No body paragraph unless the change is unusually complex and the "why" is not obvious from the diff
- Component names over file names. Write
Update validation logicnotUpdate validation.py. Use file names only when the component name is the file name (e.g.,Update configuration.yaml) - Multi-component changes. Use
andto join:Update validation and constants - No trailing period. The summary is a title, not a sentence
- No co-authors. Do not add
Co-Authored-Byor any other trailers to commit messages - No issue closers. Do not add
closes #N,fixes #N, or similar references to commit messages — issue references belong in pull requests, not commits
Version Bumps
Version bump commits use a specific format:
Update version to X.Y.Z
Examples
Good:
Add forward-slash validation to reference checksFix off-by-one in description length validationUpdate shell-scripts skill description for clarityAdd solution-design skill to .agents/Update configuration.yaml and constants for new limitFix false positive in name validation
Bad:
updated stuff— vague, no verb prefix, lowercaseFix bug— no description of what was fixedUpdate validation.py, constants.py, test_validation.py, configuration.yaml— lists files instead of describing the changeAdd new validation check for forward slashes in file references and also update the constants module to expose the new pattern and add tests— too long, multiple concernsFix: validation— colon after verb is not the convention
Edge Cases
- Reformatting or refactoring with no behavior change:
Refactoris acceptable as an additional verb:Refactor validation into separate helper functions - Test-only changes:
Add tests for forward-slash validationorUpdate tests for new edge cases - Documentation-only changes:
Update README for new distribution channels - Dependency updates:
Update coverage to 7.6.1 in requirements-dev.txt
Related Skills
milanhorvatovic/hello-router
tools
VerifiedTrustedCommunity
Greets a recipient through one of two registered tones — formal or casual — by dispatching to a dedicated capability. Activates when the conversation asks for a tone-specific welcome or a switch between formal and casual greetings; use when comparing the two styles. Demonstrates the router pattern in the Skill System Foundry — a thin SKILL.md entry point routing to capability files, with allowed-tools declared in frontmatter so capability shell fences pass validation.
1SKILL.mdUpdated Apr 29, 2026
milanhorvatovic/hello-greeter
testing
VerifiedTrustedCommunity
Greets a single recipient with a friendly welcome message rendered in a formal or casual tone. Activates when the conversation asks to say hello or welcome someone; use when a minimal standalone skill is needed. Demonstrates the smallest valid standalone skill in the Skill System Foundry — required name and description frontmatter plus an optional metadata block — and how its layout passes validation.
1SKILL.mdUpdated Apr 29, 2026
milanhorvatovic/skill-system-foundry
testing
VerifiedTrustedCommunity
Designs and evolves AI-agnostic skill systems. Triggers on skill/capability creation, role definition, or router migration; use when auditing consistency or improving token efficiency.
1SKILL.mdUpdated Apr 17, 2026
milanhorvatovic/yaml-config
development
VerifiedTrustedCommunity
Governs the configuration.yaml file that serves as the single source of truth for all validation rules in the Skill System Foundry. Triggers when adding, modifying, or reviewing validation rules, limits, patterns, or reserved words. Also triggers when working with constants.py, yaml_parser.py, or any code that reads from configuration.yaml. Use this skill when asked to add a new validation check, change a limit or threshold, update reserved word lists, add SPDX license identifiers, modify regex patterns, or troubleshoot why a validation rule is not working as expected. Activates on mentions of configuration, validation rules, constants, thresholds, or pattern definitions.
1SKILL.mdUpdated Apr 17, 2026