hermes - 💡(How to fix) Fix [Feature]: git-bisect-debugging skill

Problem or Use Case

When a regression appears and the developer doesn't know which commit introduced it, Hermes currently has no structured guidance for using git bisect to find the culprit. The systematic-debugging skill covers root-cause methodology, and test-driven-development covers writing regression tests, but neither covers the binary-search-through-history workflow that git bisect provides.

Proposed Solution

Add a git-bisect-debugging skill under skills/software-development/ that covers:

• Manual bisect workflow: identify good/bad commits, mark each step, verify the result
• Automated bisect: git bisect run with test scripts
• Common pitfalls: uncommitted changes, forgetting to reset, flaky tests, too many skips
• Quick reference: a table of the 9 core git bisect subcommands

The skill is ~135 lines, requires no external dependencies (git is universal), and works on all platforms.

Implementation

The skill is already written and tested:

• skills/software-development/git-bisect-debugging/SKILL.md - the skill
• tests/skills/test_git_bisect_skill.py - 11 smoke tests (frontmatter, sections, platforms)

All 11 tests pass.

Feature Type: New bundled skill

Scope: Small (~135 lines, single file)

• I'd like to implement this myself and submit a PR