Slash Command

/SKILL

Creates GitHub issues from a description following TDD principles, labeling conventions, and repo templates. Analyzes state, avoids duplicates, and reports issue URL.

Git

developer-tools

code-quality

npx claudepluginhub fradser/dotclaude --plugin github

Flags

Runs pre-commands

Details

Argumentdescription

Namespacecreate-issues/

Allowed Tools

TaskBash(gh:*)Bash(git:*)

Prompt Preview

# Create GitHub Issues

Execute automated GitHub issue creation workflow for $ARGUMENTS following TDD principles and conventional commit standards.

## Context

- Current git status: !`git status`
- Current branch: !`git branch --show-current`
- Open issues: !`gh issue list --state open --limit 10`
- GitHub authentication: !`gh auth status`

## Requirements Summary

Follow TDD principles, conventional commits, and protected branch workflows. Use proper labels, auto-closing keywords, and atomic commits. See `references/requirements.md` for complete standards.

## Phase 1: Repository Analysis...

Command Content

Other plugins with /SKILL

/create-issues

Creates GitHub issues from a description using TDD principles, Conventional Commits format, proper labels, and branch-aware strategy. Documents decisions and follow-ups.

3 tools

github

/create-issue

1.0k

Creates a well-structured GitHub issue interactively: prompts for type-specific details (bug/feature/task), applies templates/labels/milestones/projects, and uses GitHub API. Reports issue URL.

github-issue-manager

/issue-create

Creates a structured GitHub issue from current context or optional description. Checks for repo issue templates, drafts title/body with summary, behaviors, criteria, context, and notes.

5 tools

mach10

/create-issue

169

Creates detailed GitHub issues for features, bugs, or refactors with TDD plans, technical specs, agent instructions for PR lifecycle, and auto-labels. Accepts type/description args or prompts interactively.

metaswarm

/create-issue

Creates GitHub issue with validated labels via content analysis for type and principles, fetches repo labels, applies templates, and previews before submission.

dotfiles-commands

/SKILL

512

Executes automated project-wide refactoring across all code files, focusing on cross-file optimizations, duplication reduction, and consistency. Produces change summary with rollback info.

5 tools

refactor

Stats

Parent Repo Stars512

Parent Repo Forks39

Last CommitFeb 27, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Create GitHub Issues

Execute automated GitHub issue creation workflow for $ARGUMENTS following TDD principles and conventional commit standards.

Context

Current git status: !git status
Current branch: !git branch --show-current
Open issues: !gh issue list --state open --limit 10
GitHub authentication: !gh auth status

Requirements Summary

Follow TDD principles, conventional commits, and protected branch workflows. Use proper labels, auto-closing keywords, and atomic commits. See references/requirements.md for complete standards.

Phase 1: Repository Analysis

Goal: Assess repository state, detect templates, and determine issue scope and type.

Actions:

Analyze current branch from context (main/develop vs PR branch)
Review open issues to identify duplicates or related work
Check for contributing guidelines (CONTRIBUTING.md) and follow its requirements
Detect issue templates in .github/ISSUE_TEMPLATE/ directory
If templates exist: select appropriate template using gh issue create --list
Determine issue type (epic, PR-scoped, or review) based on $ARGUMENTS complexity
Apply branch-based decision logic from references/decision-logic.md

See references/repository-templates.md for template detection and compliance details.

Phase 2: Issue Creation

Goal: Create GitHub issue with proper structure, labels, and links.

Actions:

Create or verify required priority labels exist (see references/decision-logic.md for commands)
Draft issue following structure requirements in references/issue-structure.md
Apply appropriate labels (priority, type)
Add auto-closing keywords if PR-scoped issue (NOT for epics)
Link to related issues or epics if applicable

Phase 3: Documentation and Handoff

Goal: Document decisions and communicate follow-up actions.

Actions:

Document branch strategy decision and rationale
Report created issue number and URL to user
If on PR branch and blocking: add detailed comment to PR instead of creating issue
Share next steps (create PR, assign to team member, etc.)

References

Requirements: references/requirements.md - Full TDD and commit standards
Decision Logic: references/decision-logic.md - Branch-based decisions and issue types
Issue Structure: references/issue-structure.md - Title, labels, body, auto-closing
Repository Templates: references/repository-templates.md - Contributing guidelines and issue templates
Examples: references/examples.md - Commit message examples