Fixes #
- π Bug fix (non-breaking change that fixes an issue)
- β¨ New feature (non-breaking change that adds functionality)
- π Security fix
- π Documentation update
- β Tests (adding or improving test coverage)
- β»οΈ Refactor (no behavior change)
- π― New skill (bundled or hub)
- I've read the Contributing Guide
- My commit messages follow Conventional Commits (
fix(scope):,feat(scope):, etc.) - I searched for existing PRs to make sure this isn't a duplicate
- My PR contains only changes related to this fix/feature (no unrelated commits)
- I've run
pytest tests/ -qand all tests pass - I've added tests for my changes (required for bug fixes, strongly encouraged for features)
- I've tested on my platform:
- I've updated relevant documentation (README,
docs/, docstrings) β or N/A - I've updated
cli-config.yaml.exampleif I added/changed config keys β or N/A - I've updated
CONTRIBUTING.mdorAGENTS.mdif I changed architecture or workflows β or N/A - I've considered cross-platform impact (Windows, macOS) per the compatibility guide β or N/A
- I've updated tool descriptions/schemas if I changed tool behavior β or N/A
- This skill is broadly useful to most users (if bundled) β see Contributing Guide
- SKILL.md follows the standard format (frontmatter, trigger conditions, steps, pitfalls)
- No external dependencies that aren't already available (prefer stdlib, curl, existing Hermes tools)
- I've tested the skill end-to-end:
hermes --toolsets skills -q "Use the X skill to do Y"