Github Issue Intake

This is a Hermes-native github-issue-intake workflow skill.

Why This Exists

github-issue-intake exists so a public support-chat report can become a verified GitHub issue through one bounded, confirmation-gated lane instead of ad hoc chat narration or an unscoped bot write.

Do Not Use When

• The report only wants classification or signal clustering; use omh-feedback-triage instead.
• The event concerns an already-existing issue, PR, review, or CI run; use omh-github-event-ops instead.
• The user wants implementation; coding stays a separate follow-up lane with its own maintainer authority.
• The report describes a security vulnerability; redirect to the private SECURITY.md path.
• The issue is already decided and the user only wants it filed or edited with the gh CLI, with no chat report to classify, question, or de-duplicate; load Hermes' bundled github skill instead of this one.

Examples

Good example: