Agent Skills
› FradSer/dotclaude
› create-issues
create-issues
GitHub自动化创建GitHub Issue，遵循TDD原则和标签规范。支持分析仓库状态、选择模板、设置优先级及自动关闭关键字，并生成文档与后续指引。
Trigger Scenarios
用户要求创建issue
报告bug
记录新需求或epic
Install
npx skills add FradSer/dotclaude --skill create-issues -g -y
SKILL.md
Frontmatter
{
"name": "create-issues",
"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.",
"allowed-tools": "Task, Bash(gh:*), Bash(git:*)",
"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:
- Analyze current branch from context (main/develop vs PR branch)
- Review open issues to identify duplicates or related work
- Check for contributing guidelines (
CONTRIBUTING.md) and follow its requirements - Detect issue templates in
.github/ISSUE_TEMPLATE/directory - If templates exist: select appropriate template using
gh issue create --list - Determine issue type (epic, PR-scoped, or review) based on
$ARGUMENTScomplexity - 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:
- Create or verify required priority labels exist (see
references/decision-logic.mdfor commands) - Draft issue following structure requirements in
references/issue-structure.md - Apply appropriate labels (priority, type) using
--label- Assign owners using
--assignee - Link milestones using
--milestoneor projects using--projectif requested
- Assign owners using
- 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.mdfor the full rule and keyword table.
- 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
- Link to related issues or epics if applicable
Phase 3: Documentation and Handoff
Goal: Document decisions and communicate follow-up actions.
Actions:
- Document branch strategy decision and rationale
- Report created issue number and URL to user
- If on PR branch and blocking: add detailed comment to PR instead of creating issue
- 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
Version History
- 6f2a0b2 Current 2026-08-20 10:58
