Skip to main content
skill CX Codex

create-issues — Claude Code skill: GitHub issues with TDD and auto-closing

create-issues automates GitHub issue creation with TDD principles, proper labeling, and auto-closing keywords. Detects repository templates, applies conventions, and links issues to epics or related tasks.

MIT 116 installs ★ 597 updated 2026-10-09

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add FradSer/dotclaude --skill create-issues -a claude-code
Open on GitHub

What create-issues does

The skill runs three phases: repository analysis to find templates and guidelines, issue creation with labels and auto-closing keywords, and documentation of decisions. It checks for duplicates in open issues, respects branch strategy (main vs PR branch), and drafts issues following TDD standards.

One critical rule: auto-closing keywords only fire when a PR merges into the repository's default branch. If the issue will be resolved by a PR targeting a different branch, the skill warns that manual closure is needed.

Installation varies by platform: npx skills add for Claude Code, Codex, Cursor, Gemini CLI, and OpenCode; gh skill install for GitHub Copilot. Requires active GitHub authentication and gh and git command access.

What it helps with

  • create a GitHub issue using the repository template with correct labels
  • document a bug or requirement following TDD conventions and commit standards
  • add auto-closing keywords to close the issue when a PR merges
  • link a new issue to an epic or related open tasks
  • check for duplicate issues before filing

Example prompts for the agent

  • Create an issue for a critical bug with high priority labeling
  • Document a new feature requirement using the repository template
  • File a PR-scoped issue that closes automatically when merged to main

How to install create-issues

1Skills CLI (Vercel)

npx skills add FradSer/dotclaude --skill create-issues -a claude-code

2Manually: put the files in place

~/.claude/skills/create-issues/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/create-issues/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about create-issues

How do I install create-issues in Claude Code?

Run npx skills add FradSer/dotclaude --skill create-issues -a claude-code, then open ~/.claude/skills/create-issues/SKILL.md. For other platforms: Codex uses --skill create-issues -a codex, GitHub Copilot uses gh skill install FradSer/dotclaude create-issues.

What does create-issues do?

It automates GitHub issue creation: analyzes your repository, applies templates, adds labels and priority tags, and sets up auto-closing keywords for PR-scoped work. Enforces TDD and conventional commit standards.

When do auto-closing keywords not work?

Auto-closing only activates when a PR merges into the default branch. If your PR targets a different branch, the issue stays open and must be closed manually.

Source text

SKILL.md · MIT
---
name: create-issues
allowed-tools: Task, Bash(gh:*), Bash(git:*)
description: 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.
argument-hint: [description]
user-invocable: true
---

# 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

© FradSer · MIT · FradSer/dotclaude

Similar skills

All skills for Git and GitHub →

From the same set16

The whole set →

Project sponsors

Companies that keep this analytics open