gh-ticket
Create and update comprehensive GitHub issues with full technical context to prevent requirement loss and reduce implementation friction.
Introduction
This skill acts as a technical documentation assistant for the GitHub issue lifecycle. It is designed for engineers, team leads, and project managers who want to eliminate the 'vague ticket' problem by enforcing a rigorous capture of system state, technical evidence, and specific requirements at the moment an idea or bug is first identified. By ensuring that context is captured while it is still fresh in the agent's memory, the tool bridges the gap between intent and implementation, preventing the common issue where technical nuances are forgotten during the development cycle.
-
Automated context extraction: Prompts the user to document trigger sources, relevant file paths, error messages, and current vs. desired state.
-
Technical evidence gathering: Includes pre-configured patterns for executing git log commands, file searching via grep, and cross-referencing existing issues or pull requests using the GitHub CLI (gh).
-
Structured requirements modeling: Enforces a standardized template containing functional requirements, specific edge cases, and verifiable acceptance criteria to ensure definition of done.
-
Implementation guidance: Structures notes for the developer, including lists of affected files (modify/create/delete), key code locations, and dependency tracking.
-
Standardized documentation: Promotes consistent issue tracking across projects by using a mandatory template structure for every ticket created.
-
Best for: Capturing complex bugs, planning new features, or documenting investigative findings that require action.
-
Workflow: Follows a four-phase process: Context Capture, Requirements Extraction, Implementation Guidance, and standard Ticket Structure generation.
-
Key inputs/outputs: Takes developer investigation notes and technical context; outputs a fully formatted, high-context GitHub issue ready for team consumption.
-
Constraints: Requires access to the GitHub CLI (gh) for optimal cross-referencing and assumes a collaborative environment where tickets are the primary source of truth for development tasks.
Repository Stats
- Stars
- 3
- Forks
- 1
- Open Issues
- 3
- Language
- Shell
- Default Branch
- main
- Sync Status
- Idle
- Last Synced
- May 1, 2026, 09:14 AM