MCPInstall

create-issues

by fradserCode Quality & Workflow

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.

Installs
115
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

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

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads create-issues automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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

FAQ

What does the create-issues skill do?

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.

How do I install create-issues?

Run npx skills add https://github.com/fradser/dotclaude --skill create-issues in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/create-issues/ (personal) or .claude/skills/create-issues/ (project).

Which AI agents can use create-issues?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is create-issues safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains create-issues?

It is published by fradser in fradser/dotclaude. It has 115 recorded installs.

More from fradser/dotclaude

View all →

patent-architect

fradser/dotclaude

Automatically searches prior art via SerpAPI and generates Chinese patent application forms. This skill should be used when the user wants to generate Chinese patent application forms, or mentions "patents", "inventions", or wants to protect technical innovations.

Media & Creative618 installs

agent-browser

fradser/dotclaude

Open the skill to read its SKILL.md instructions.

Productivity & Automation156 installs

behavior-driven-development

fradser/dotclaude

Applies behavior-driven development principles including Gherkin scenarios and test-driven development. This skill should be used when the user asks to implement features, fix bugs, or when writing executable specifications and tests before writing production code.

Testing & QA148 installs

commit-and-push

fradser/dotclaude

Creates clean conventional git commits using standard git and pushes changes to the remote repository. Use when the user asks to "commit and push", "push changes", or complete a commit followed by git push.

Code Quality & Workflow125 installs

executing-plans

fradser/dotclaude

Executes a written implementation plan via per-batch sub-agent coordinators with verification and commits between batches.

Code Quality & Workflow125 installs

brainstorming

fradser/dotclaude

Open the skill to read its SKILL.md instructions.

123 installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Code Quality & Workflow1.4M installs

improve-codebase-architecture

mattpocock/skills

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Code Quality & Workflow1.2M installs

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

Code Quality & Workflow1.1M installs

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

Code Quality & Workflow890.6K installs

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Code Quality & Workflow863.8K installs

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

Code Quality & Workflow848.4K installs