skills.rest
jarosser06
jarosser06COMMUNITY
Explore all skills by this author →
GitHub

Issue Writing

Define and enforce objective GitHub issue writing standards for the da_vinci project.

3|Updated Jan 30, 2024
Search Tags:#github#bugs#features#labels#acceptance-criteria#issue-writing#issue-template
One-click install
npx skills add https://github.com/jarosser06/da-vinci --skill issue-writing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Issue Writing
Source: https://github.com/jarosser06/da-vinci/tree/main/.claude/skills/issue-writing
Command: npx skills add https://github.com/jarosser06/da-vinci --skill issue-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issue creation often lacks consistency, leading to miscommunication and delays in addressing problems. This Skill provides clear guidelines to create, format, and label issues with objective language and verifiable criteria.

Core Features & Use Cases

  • Provides standardized templates for Bug, Feature, and Task issues.
  • Enforces objective language and explicit acceptance criteria to improve clarity and reviewability.
  • Helps teams quickly craft high-quality issues that align with project standards.

Quick Start

Create a new issue using the appropriate template and fill in the required sections.

Frequently Asked Questions about Issue Writing

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

FAQPage Schema
How do I standardize GitHub issue writing for bugs and features?▼

To standardize GitHub issue writing, apply structured templates with explicit acceptance criteria for Bug, Feature, and Task types. This enforces consistent formatting and labeling, ensuring clear and verifiable project requirements.

What are GitHub issue templates with acceptance criteria?▼

GitHub issue templates with acceptance criteria are standardized formats enforcing objective language and structured sections. They guide users to define clear, verifiable requirements for bugs and features, reducing miscommunication and review delays.

How do I write objective acceptance criteria for a GitHub feature request?▼

Write objective acceptance criteria for a GitHub feature request by using explicit, verifiable language within a standardized template. This ensures requirements are clear and testable, aligning the issue with project standards for faster review.

How do I format and label GitHub issues consistently?▼

Format and label GitHub issues consistently by applying predefined templates for Bug, Feature, and Task types. These templates require structured sections and objective language, ensuring every issue meets your project's formatting standards.

Why does my GitHub issue lack clear requirements?▼

Your GitHub issue lacks clear requirements if it misses structured sections and objective acceptance criteria. Applying standardized issue templates enforces verifiable language, transforming vague descriptions into clear, reviewable tasks.

Related Skills

Explore More Content & Communication Skills→
J-StaR-Films-StudiosJ-StaR-Films-Studios
23

github-ops

Automate GitHub issue management, project board sync, and label creation via gh CLI.

Official
Intermediate
gioegioe

address-issue

Convert GitHub issues into tusk tasks with acceptance criteria.

Community
Advanced
EmasoftEmasoft
1

amama-github-routing

Route GitHub issues, PRs, projects, and releases to specialists using team labels and UUID tracking.

Community
Advanced
alexandereiseghohialexandereiseghohi

gh-cli

Manage GitHub repositories, issues, pull requests, and Actions from the terminal.

Community
Advanced