issue-conventions

Enforce GitHub issue creation conventions with templates and mandatory assignees.

2|Updated Nov 12, 2025
One-click install
npx skills add https://github.com/stlwolf/ai-development-hub --skill issue-conventions
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: issue-conventions
Source: https://github.com/stlwolf/ai-development-hub/tree/main/canonical/skills/issue-conventions
Command: npx skills add https://github.com/stlwolf/ai-development-hub --skill issue-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces standardized issue creation rules to ensure consistent task tracking and proper use of GitHub's issue creation commands.

Core Features & Use Cases

  • Template-aware: automatically selects appropriate templates from .github/ISSUE_TEMPLATE when creating issues.
  • CLI compliance: enforces proper gh issue create usage and mandatory fields like assignee.
  • Guidance for initialization: provides clear instructions on how to start work via issues.

Quick Start

Create a new issue following the conventions and specify the assignee and template when initiating gh issue create.

Frequently Asked Questions about issue-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce GitHub issue creation conventions using the gh CLI?β–Ό

You can enforce GitHub issue creation conventions by validating gh issue create commands, ensuring templates are selected from .github/ISSUE_TEMPLATE, and requiring a mandatory assignee for standardized task tracking.

Can I automatically select issue templates from .github/ISSUE_TEMPLATE when creating issues?β–Ό

Yes, template-aware issue creation automatically selects appropriate templates from the .github/ISSUE_TEMPLATE directory when you initiate the gh issue create workflow.

Does GitHub issue creation require a mandatory assignee for CLI compliance?β–Ό

Yes, CLI compliance for GitHub issue creation enforces a mandatory assignee field, ensuring every issue created via gh issue create is properly assigned for task tracking.

What is the best way to standardize task tracking across GitHub teams?β–Ό

Standardizing task tracking across teams involves enforcing consistent issue creation rules, applying template selection constraints, and validating gh issue create usage to maintain uniform task records.

Why does gh issue create fail without following issue conventions?β–Ό

The gh issue create command fails without following issue conventions because the enforcement validates proper CLI usage, checks for mandatory assignees, and verifies template selection from .github/ISSUE_TEMPLATE.