create-github-issue
Create GitHub issues using GitHub CLI with support for templates, labels, assignees, milestones, and draft issues. Use when the user asks to create a GitHub issue, file a bug report, submit a feature request, or open an issue in a GitHub repository.
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 7637
- Лиценз
- Apache-2.0
- Последна проверка на записа
- 21.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add tailcallhq/forgecodeСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
Create GitHub Issue
Create comprehensive GitHub issues using gh issue create by dynamically discovering and adhering to the repository's official issue templates.
Workflow
1. Discover and Select Template
CRITICAL: You must use the repository's official templates. Do not assume the structure.
- List available templates:
ls .github/ISSUE_TEMPLATE/ - Select the most appropriate template based on the issue type (e.g.,
bug_report.yml,feature_request.yml). - Read the selected template to understand its required fields, structure, and any title prefixes or default labels.
cat .github/ISSUE_TEMPLATE/<selected_template>.yml
2. Gather Context
Gather relevant information to fulfill the template requirements:
# Check current git status for context
git status
# View recent commits if related to codebase changes
git log --oneline -10
# Check if related issues exist
gh issue list --search "keyword" --limit 10
3. Generate Markdown Body
MANDATORY: Structure the issue body exactly as defined in the selected YAML template without exception.
- Map YAML fields to Markdown: Convert each field in the template (typically found under
body:) into a Markdown section. - Use Headers: Use the
labeloridfrom the YAML field as an H2 header (e.g.,## Bug Description). - Respect Validation: Ensure all fields marked as
required: truein the YAML are populated with meaningful content. - Format Correctly: Use code blocks (e.g.,
```shell,```yaml) for logs and configurations as suggested by the template'srenderattribute.
4. Choose Labels
Select labels by inspecting .github/labels.json.
- Primary Label: Always include a
type:label that matches the issue type. - Additional Labels: Add relevant
state:,work:, orpriority:labels if they exist in the configuration. - Constraint: Only use labels defined in
.github/labels.json.
5. Create Title
Follow the template's title field if it provides a prefix (e.g., "[Bug]: ").
- Be concise: Keep under 70 characters.
- Use imperative mood: "Fix authentication timeout" instead of "Authentication is timing out".
- Start with action verb: Fix, Add, Improve, Update, Refactor.