Skip to content

Latest commit

Β 

History

History
75 lines (47 loc) Β· 3.04 KB

File metadata and controls

75 lines (47 loc) Β· 3.04 KB

What does this PR do?

Related Issue

Fixes #

Type of Change

  • πŸ› 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)

Changes Made

How to Test

Checklist

Code

  • 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/ -q and all tests pass
  • I've added tests for my changes (required for bug fixes, strongly encouraged for features)
  • I've tested on my platform:

Documentation & Housekeeping

  • I've updated relevant documentation (README, docs/, docstrings) β€” or N/A
  • I've updated cli-config.yaml.example if I added/changed config keys β€” or N/A
  • I've updated CONTRIBUTING.md or AGENTS.md if 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

For New Skills

  • 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"

Screenshots / Logs