mcpField
C
create-issues

create-issues

github.com/fradserDevelopment596115 installsUpdated 5w ago
Repository

About create-issues

A development skill that guides an automated workflow for creating GitHub issues, from repository review through issue drafting and handoff. It emphasizes branch-aware decisions, repository templates, labels, and issue-closing rules.

Key features

  1. 01Review repository state and open issues
  2. 02Detect contributing guides and issue templates
  3. 03Choose issue scope based on branch and complexity
  4. 04Draft issues with labels and links
  5. 05Document decisions and follow-up steps

Use cases

  1. 01Create a repository issue while checking for duplicates
  2. 02Prepare an issue that follows repository templates
  3. 03Handle work tied to a pull request branch
  4. 04Link issues to milestones, projects, or related work

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/fradser/dotclaude --skill create-issues

After installing, type/create-issuesin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
decision-logic.md
issue-structure.md
requirements.md

Details

From the project README

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) using --label
    • Assign owners using --assignee
    • Link milestones using --milestone or projects using --project if requested
  4. Add auto-closing keywords if PR-scoped issue (NOT for epics)
    • CRITICAL: auto-closing keywords only fire when the PR merges into the repository's default branch. If the issue will be resolved by a PR targeting a non-default branch, warn the user that the issue will NOT close automatically and must be closed manually — see references/auto-closing-keywords.md for the full rule and keyword table.
  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
  • Auto-Closing Keywords: references/auto-closing-keywords.md - Default-branch limitation and keyword table
  • Repository Templates: references/repository-templates.md - Contributing guidelines and issue templates
  • Examples: references/examples.md - Commit message examples

Comments

Markdown supported