Problem
The skill relies on Claude Code's LLM interpretation to enforce workflow rules. Teams that want mechanical enforcement alongside the skill have no guidance on how to set up:
- Pre-commit hooks (e.g., husky, pre-commit) for commit message validation
- commit-msg validators (e.g., commitlint) to enforce Conventional Commits format
- Branch name linting to enforce the naming convention
- CI/CD integration to validate PR titles match Conventional Commits
Expected behavior
Add an "Integration" section to SKILL.md (or a separate INTEGRATIONS.md linked from README) covering:
- Recommended tools for mechanical enforcement
- Example commitlint config that matches the skill's Conventional Commits rules
- Example husky/pre-commit setup
- How these tools complement (not replace) the skill
Keep it concise — config snippets and links to official docs, not full tutorials.
Problem
The skill relies on Claude Code's LLM interpretation to enforce workflow rules. Teams that want mechanical enforcement alongside the skill have no guidance on how to set up:
Expected behavior
Add an "Integration" section to SKILL.md (or a separate INTEGRATIONS.md linked from README) covering:
Keep it concise — config snippets and links to official docs, not full tutorials.