Agent skill

create-issues

Creates GitHub issues following test-driven development principles and proper labeling conventions. This skill should be used when the user asks to "create an issue", "file a bug", or needs to document new requirements, epics, or PR-scoped tasks.

Stars 521
Forks 40

Install this agent skill to your Project

npx add-skill https://github.com/FradSer/dotclaude/tree/main/github/skills/create-issues

SKILL.md

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:

  1. Analyze current branch from context (main/develop vs PR branch)
  2. Review open issues to identify duplicates or related work
  3. Check for contributing guidelines (CONTRIBUTING.md) and follow its requirements
  4. Detect issue templates in .github/ISSUE_TEMPLATE/ directory
  5. If templates exist: select appropriate template using gh issue create --list
  6. Determine issue type (epic, PR-scoped, or review) based on $ARGUMENTS complexity
  7. 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:

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

Phase 3: Documentation and Handoff

Goal: Document decisions and communicate follow-up actions.

Actions:

  1. Document branch strategy decision and rationale
  2. Report created issue number and URL to user
  3. If on PR branch and blocking: add detailed comment to PR instead of creating issue
  4. 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

Expand your agent's capabilities with these related and highly-rated skills.

FradSer/dotclaude

optimize-plugin

This skill should be used when the user asks to "validate a plugin", "optimize plugin", "check plugin quality", "review plugin structure", or "run plugin optimizer".

521 40
Explore
FradSer/dotclaude

plugin-best-practices

This skill should be used when the user asks to "validate plugin structure", "review manifest files", "check frontmatter compliance", "verify tool invocation patterns", "explain plugin component types", or needs Claude Code plugin architectural guidance.

521 40
Explore
FradSer/dotclaude

init-config

Generates a CLAUDE.md file with AI-driven environment detection and advanced configuration options. This skill should be used when the user asks to "initialize config", "setup claude config", "create CLAUDE.md", or needs help configuring project instructions.

521 40
Explore
FradSer/dotclaude

start-feature

Starts working on a new feature branch using git-flow. This skill should be used when the user asks to "start a feature", "create feature branch", "begin new feature", "git flow feature start", or wants to start a new feature.

521 40
Explore
FradSer/dotclaude

finish-feature

Finalizes and merges a feature branch into develop using git-flow. This skill should be used when the user asks to "finish a feature", "merge feature branch", "complete feature", "git flow feature finish", or wants to finalize a feature branch.

521 40
Explore
FradSer/dotclaude

finish-hotfix

Finalizes a hotfix and merges it into main and develop using git-flow. This skill should be used when the user asks to "finish a hotfix", "merge hotfix branch", "complete hotfix", "git flow hotfix finish", or wants to finalize a hotfix.

521 40
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results