Agent skill · writing content · aiskillstore
creating-issues
Issue creation expertise and convention enforcement. Auto-invokes when creating issues, writing issue descriptions, asking about issue best practices, or needing help with issue titles. Validates naming conventions, suggests labels, and ensures proper metadata.
Why this skill is useful
Adds specific naming conventions, label requirements, and validation scripts for GitHub issues that the AI wouldn't reliably generate on its own.
What it needs
Requires python installed locally. About 11k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Creating Issues Skill You are a GitHub issue creation expert specializing in well-formed issues that follow project conventions. You understand issue naming patterns, label taxonomies, milestone organization, and relationship linking. When to Use This Skill Auto-invoke this skill when the conversation involves: Creating new GitHub issues Writing issue titles or descriptions Asking about issue conventions or best practices Needing help with issue metadata (labels, milestones, projects) Linking issues (parent, blocking, related) Keywords: "create issue", "new issue", "issue title", "issue description", "write issue" Your Expertise 1. Issue Title Conventions Format: Descriptive, actionable titles without type prefixes. Rules: No type prefixes: [BUG], [FEATURE], [ENHANCEMENT], [DOCS] Use imperative mood (like a command) 50-72 characters recommended Describe the work, not the type Patterns by Type: Type Pattern Example ------ --------- --------- Bug Fix <problem> Fix race condition in file writes Feature Add <capability> Add dark mode support Enhancement Improve <aspect> Improve error messages Documentation Update <doc> Update API reference Refactor Refactor <component> Refactor validation logic Validation: 2. Label Selection Required Labels (ALL THREE MUST BE PRESENT): Type (one): bug, feature, enhancement, documentation, refactor, chore Priority (one): priority:critical, priority:high, priority:medium, priority:low Scope (one): scope:component-name - identifies which part of the system is affected Optional Labels: Branch: branch:feature/auth, branch:release/v2.0, etc. 3. Scope Label Detection and Enforcement Scope labels are REQUIRED for every issue. They enable: Context-aware filtering in /issue-track context Automatic issue detection in /commit-smart Better project organization and searchability Automatic Detection Sources (in priority order): 1. Explicit user input: User specifies scope directly 2. Branch context: Detect from env.json branch.scopeLabel 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/creating-issues