gh-issue_skill
- Go
3
GitHub Stars
3
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill linehaul-ai/linehaulai-claude-marketplace --skill gh-issue- examples.md5.1 KB
- README.md4.3 KB
- SKILL.md3.1 KB
Overview
This skill creates well-structured GitHub issues from conversation context, automatically organizing work into parent issues with sub-tasks and clear acceptance criteria. It converts informal discussions, plans, or bug reports into trackable, reviewable issues with proper formatting and links back to GitHub. Use it to keep work visible and actionable across planning and development.
How this skill works
I analyze the current conversation and any referenced implementation notes to determine scope, goals, and discrete tasks. The agent then generates descriptive issue titles, detailed descriptions with acceptance criteria, and parent/child relationships, and creates sub-tasks that map to the implementation plan. Finally, the skill returns direct GitHub links so you can review, assign, and triage the created issues.
When to use it
- Convert a planning discussion or chat thread into tracked GitHub issues
- Break a complex feature into a parent issue with actionable sub-tasks
- Group and track related bugs under a single parent for easier triage
- Create issues from a to-do list or implementation plan after meetings
- Ensure follow-up work isn’t lost after design or review conversations
Best practices
- Be specific: name the feature or bug and list desired sub-tasks
- Include acceptance criteria or expected behavior for each task
- Reference relevant files, designs, or conversation timestamps when available
- Indicate priority or estimate to help with triage and scheduling
- Review generated issue descriptions and tweak labels or assignees before closing
Example use cases
- After a design meeting, create a parent issue for a new onboarding flow with child tasks for UI, API, and tests
- Turn a Slack bug thread into a parent issue listing each reproducible bug as a sub-task
- Create issues for remaining work items from a retrospective or planning doc
- Break down a new billing workflow into discrete implementation steps with acceptance criteria
- Convert a product conversation into prioritized issues ready for sprint planning
FAQ
Yes. It structures complex work into a parent issue and creates child sub-tasks that map to the implementation plan.
What information should I provide for best results?
Provide a brief summary of the feature or bug, list desired sub-tasks, and include acceptance criteria or references to designs when possible.