Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From github
Enforces issue structure standards including title format, labels, body templates for bugs/features/epics, YAML form schemas, auto-closing keywords, and template compliance.
How this command is triggered — by the user, by Claude, or both
Slash command
/github:issue-structurecreate-issues/references/The summary Claude sees in its command listing — used to decide when to auto-load this command
# Issue Structure Requirements ## Title - Maximum 70 characters - Imperative mood, no emojis - Optional prefix: `[Bug]`, `[Feature]`, `[Epic]` ## Labels - Priority: `priority:high`, `priority:medium`, `priority:low` - Type: `bug`, `feature`, `enhancement`, `documentation` ## Body Template ### Bug Report ### Feature Request ### Epic ## Issue Forms (YAML) When project uses YAML forms, detect and follow the schema: ## Auto-Closing Keywords | Keyword | Example | Behavior | |---------|---------|----------| | Closes | `Closes #123` | PR merges → issue closes | | Fixes | `Fixes...
[Bug], [Feature], [Epic]priority:high, priority:medium, priority:lowbug, feature, enhancement, documentation## Description
Clear description of the bug
## Steps to Reproduce
1. Go to '...'
2. Click on '...'
3. See error
## Expected Behavior
What should happen
## Environment
- OS:
- Version:
## Problem
What problem does this solve
## Proposed Solution
What you want to happen
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
## Overview
High-level description and business value
## Child Issues
- #123 - Issue title
- #124 - Issue title
## Success Metrics
How to measure success
When project uses YAML forms, detect and follow the schema:
name: Bug Report
title: "[Bug]: "
labels: ["bug"]
body:
- type: textarea
id: description
attributes:
label: Description
validations:
required: true
| Keyword | Example | Behavior |
|---|---|---|
| Closes | Closes #123 | PR merges → issue closes |
| Fixes | Fixes #123 | PR merges → issue closes |
| Resolves | Resolves #123 | PR merges → issue closes |
Rules:
When project has issue templates:
gh issue create --listnpx claudepluginhub tiiwoo/dotclaude --plugin github3plugins reuse this command
First indexed Mar 13, 2026
/issue-structureEnforces issue structure standards including title format, labels, body templates for bugs/features/epics, YAML form schemas, auto-closing keywords, and template compliance.
/issueCreates a well-structured GitHub issue with dedup and validation, ready for pipeline consumption. Supports interactive and programmatic invocation with --dry-run, --title, --body, --body-file flags.
/create-issueCreates a new GitHub issue with formatted body, labels, assignees, milestones, and reference links to related content.
/issue-createCreates a structured GitHub issue from current context or description, with optional template selection and meta-directive handling.
/create-issueCreates GitHub issue with validated labels via content analysis for type and principles, fetches repo labels, applies templates, and previews before submission.
/SKILLGenerates a structured GitHub Issue with title, body, and optional plan section, incorporating context from challenge, research, and think artifacts.