gh-ticket

Create a GitHub issue by capturing investigation findings, error messages, code state, and implementation notes in a structured format. This Skill enforces a phased workflow that gathers technical evidence, extracts functional and edge-case requirements, defines acceptance criteria, and produces a ready-to-create ticket with all required sections and evidence included.

Include context dump (user request, errors, dependencies, environment), requirements extraction (functional specs and edge cases), acceptance criteria, implementation notes, and files to modify. Capturing these elements at ticket creation—when you have maximum context—ensures developers have complete information without referencing scattered investigation findings.

Yes. This Skill produces standardized ticket templates for bug reports and feature requests that structure all required sections: context, requirements, edge cases, acceptance criteria, and implementation details. Templates enforce consistent formatting across GitHub issues.

Document findings and investigation into structured Requirements and Edge Cases sections within the ticket. The Skill converts your investigation findings, error messages, and code state into formal functional requirements and edge-case specifications that acceptance criteria can reference.

Include Implementation Notes that specify files to modify and create, linking ticket sections to concrete code locations. This traceability ensures developers understand what the ticket asks and where changes belong before implementation begins.

No. This Skill organizes investigation findings, error messages, requirements, and implementation notes into a structured ticket automatically, eliminating manual assembly and ensuring no context is lost between discovery and implementation phases.