write-issue

Create GitHub issues with enforced formatting, labels, and AI-Scrum board fields.

9|2|Updated Nov 29, 2024
One-click install
npx skills add https://github.com/bbvch-ai/aihub-core --skill write-issue-bbvch-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-issue
Source: https://github.com/bbvch-ai/aihub-core/tree/main/.claude/skills/write-issue
Command: npx skills add https://github.com/bbvch-ai/aihub-core --skill write-issue-bbvch-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

Manually creating GitHub issues for the aihub-core project that adhere to the team's strict formatting, labeling, and board tracking conventions is time-consuming and error-prone, leading to inconsistent issues that do not meet review standards and are often missed in sprint planning.

Core Features & Use Cases

  • Convention Enforcement: Automatically applies the project's required title format, body structure (In scope / Out of scope / Accepted when sections), and labeling rules to new issues.
  • Board Integration: Adds newly created issues directly to the AI-Scrum project board with correct Item Type, Status, and Priority fields pre-populated.
  • Validation & Relationship Wiring: Runs post-creation checks to confirm issue compliance, and supports linking parent epics, child issues, and blocked-by dependencies.
  • Use Case: A developer filing a bug for a RAG agent crash can use this skill to generate a properly formatted issue with the correct area labels, set its priority to P1, add it to the sprint board, and link it to the relevant parent epic in seconds, with no manual formatting or board editing required.

Quick Start

Use the write-issue skill to create a new bug report for the RAG agent crashing on image nodes, set its priority to P1, and add it to the AI-Scrum board.

Frequently Asked Questions about write-issue

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

FAQPage Schema
How do I enforce a consistent title and body format for GitHub issues in a project?

You can enforce consistent GitHub issue formatting by using a script that automatically applies the required title format, body structure sections, and labeling rules to new issues, ensuring they pass review standards.

How do I automatically add new GitHub issues to a sprint planning project board?

To add new GitHub issues to a sprint board automatically, configure a creation script that pre-populates the Item Type, Status, and Priority fields on your AI-Scrum project board during issue generation.

Can I link parent epics, child issues, and blocked-by dependencies when creating a GitHub issue?

Yes, you can wire cross-issue relationships by running post-creation checks that link parent epics, child issues, and blocked-by dependencies immediately after the GitHub issue is created.

What's the best way to assign area and version labels to bug reports on GitHub?

The best way to assign area and version labels to bug reports is using an automated convention enforcement script that applies project-specific labels during issue creation, preventing manual labeling errors.

Do I need the GitHub CLI installed to automate issue creation and validation?

Yes, you need the GitHub CLI and jq installed to run the scripts that automate issue creation, apply formatting conventions, and execute post-creation validation checks.

Why do my manually created GitHub issues keep failing sprint planning reviews?

Manually created GitHub issues fail sprint planning reviews when they lack the strict body structure, required labels, or board tracking fields, which an automated convention enforcement script prevents.