home / skills / linehaul-ai / linehaulai-claude-marketplace / gh-issue

This skill creates well-structured GitHub issues from conversation, organizing work into parent issues with sub-tasks and clear acceptance criteria.

npx playbooks add skill linehaul-ai/linehaulai-claude-marketplace --skill gh-issue

Review the files below or copy the command above to add this skill to your agents.

Files (3)
SKILL.md
3.1 KB
---
name: gh-issue
description: Create structured GitHub issues with sub-tasks and proper formatting. Use when organizing development work into trackable issues, breaking down features into parent/child issues, converting discussions into tracked work, or creating issues from conversation context.
keywords: [github, github-issues, automation, task-management, issue-tracking]
---

# GitHub Issue Creator

## Overview

This Skill helps you create well-structured GitHub issues directly from conversation context. It automatically organizes complex work into parent issues with sub-tasks, ensuring nothing gets lost in discussion.

## When to Use This Skill

Use this when you want to:

- **Convert discussions into tracked work** - Turn feature discussions into properly structured GitHub issues
- **Break down complex features** - Create parent issues with sub-tasks for multi-step work
- **Organize related bugs** - Group related issues under a parent for better tracking
- **Track implementation work** - Create issues aligned with the to-do tree structure
- **Ensure work isn't forgotten** - Proactively create issues after discussing features or improvements

## How It Works

When you ask to create GitHub issues, I'll:

1. **Analyze the conversation context** to understand what needs to be tracked
2. **Use the gh-issue-creator agent** to create properly structured issues with:
   - Clear, descriptive titles
   - Detailed descriptions with acceptance criteria
   - Parent/child relationships for complex work
   - Sub-tasks that align with the implementation plan
3. **Provide GitHub links** so you can review and manage the issues

## Example Usage

### After Feature Discussion
```
"Create GitHub issues for the carrier onboarding feature we just discussed"
```

### Breaking Down Work
```
"Create a parent issue for the new billing workflow with sub-tasks for:
- POD receipt handling
- Invoice ready flag logic
- Payment tracking"
```

### Organizing Related Bugs
```
"Create a parent issue for the load status bugs with individual sub-tasks for each problem"
```

### From Existing Plan
```
"Create GitHub issues for the remaining work we discussed"
```

## Agent Delegation

When you request issue creation, I'll delegate to the **gh-issue-creator** agent, which has access to:

- Current conversation context
- Your repository structure
- GitHub CLI (`gh`) for issue creation
- Understanding of parent/child issue relationships

The agent will create issues that match your discussion and provide you with direct links to review them in GitHub.

## Tips for Best Results

- **Be specific** about what features or bugs need tracking
- **Mention sub-tasks** if you want them broken down
- **Reference earlier discussion** - the agent has full conversation context
- **Review the created issues** using the GitHub links provided

## Integration with Workflow

This Skill works seamlessly with:

- **Todo lists** - Convert completed todos into documented issues
- **Planning discussions** - Create issues from implementation plans
- **Bug reports** - Track bugs with proper sub-task breakdown
- **Feature requests** - Organize feature work into manageable pieces

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

Can the skill create parent/child issue relationships automatically?

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.