create-issues

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

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "create-issues" with this command: npx skills add fradser/dotclaude/fradser-dotclaude-create-issues

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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

behavior-driven-development

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

agent-team-driven-development

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

next-devtools-guide

No summary provided by upstream source.

Repository SourceNeeds Review