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.
Best use case
create-issues is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using create-issues should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/create-issues/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How create-issues Compares
| Feature / Agent | create-issues | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this 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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# 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
Related Skills
create-prd
This skill should be used when the user asks to "create PRD", "write product requirements document", or mentions "PRD", "产品需求文档", "创建PRD", "写PRD", "生成PRD".
create-feishu-doc
Automates creating new documents in the Feishu workspace. This skill should be used when the user asks to "create a Feishu doc", "create a new doc in Feishu", "open Feishu and create document", "create document in leiniao-ibg", or mentions creating documents in Feishu or Lark workspace.
resolve-issues
Resolves GitHub issues using isolated worktrees and test-driven development. This skill should be used when the user asks to "resolve an issue", "fix issue
create-pr
Creates comprehensive GitHub pull requests with automated quality validation and security scanning. This skill should be used when the user asks to "create a PR", "submit a pull request", or needs to merge completed work with full compliance checks.
update-readme
Updates README.md and README.zh-CN.md to reflect the project's current state. Use this skill whenever the user asks to "update the README", "sync the docs", "update documentation", "reflect latest changes in README", or wants both the English and Chinese READMEs to match the current project. Always triggers when the user mentions updating or regenerating README files, especially for bilingual (EN/ZH) projects.
swiftui-review
Reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. This skill should be used when the user asks to review SwiftUI code, check for deprecated iOS/macOS APIs, validate data flow patterns, or audit accessibility compliance in Swift projects.
writing-plans
Creates executable implementation plans that break down designs into detailed tasks. This skill should be used when the user has completed a brainstorming design and asks to "write an implementation plan" or "create step-by-step tasks" for execution.
systematic-debugging
Provides a systematic debugging methodology with a 4-phase root cause analysis process. This skill should be used when the user reports a bug, error, test failure, or unexpected behavior, ensuring thorough investigation precedes any code changes.
need-vet
This skill should be used when the user invokes /need-vet to enable work verification for the current task. Claude must verify completion and append the verified tag before the session can end.
executing-plans
Executes written implementation plans efficiently using agent teams or subagents. This skill should be used when the user has a completed plan.md, asks to "execute the plan", or is ready to run batches of independent tasks in parallel following BDD principles.
build-like-iphone-team
Applies Apple's Project Purple design philosophy for radical innovation. This skill should be used when the user wants to challenge industry conventions, approach open-ended problems requiring disruptive thinking, or when standard brainstorming needs a breakthrough approach.
brainstorming
Structures collaborative dialogue to turn rough ideas into implementation-ready designs. This skill should be used when the user has a new idea, feature request, ambiguous requirement, or asks to "brainstorm a solution" before implementation begins.