skills.rest
Jitsusama
JitsusamaCOMMUNITY
Explore all skills by this author →
GitHub

issue-writing

Create structured GitHub issues with clear titles and acceptance criteria.

6|3|Updated Mar 8, 2026
Search Tags:#documentation#github#cli#issue tracking#bug report#feature request
One-click install
npx skills add https://github.com/Jitsusama/agentic-harness.pi --skill issue-writing-jitsusama
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-writing
Source: https://github.com/Jitsusama/agentic-harness.pi/tree/main/skills/issue-writing
Command: npx skills add https://github.com/Jitsusama/agentic-harness.pi --skill issue-writing-jitsusama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you write clear, actionable GitHub issues that effectively communicate the problem, desired outcome, and acceptance criteria, ensuring better project alignment and faster development.

Core Features & Use Cases

  • Structured Issue Creation: Learn conventions for issue titles and body structure.
  • Heredoc CLI Format: Understand how to use heredocs for reliable issue creation via the command line, avoiding character escaping issues.
  • Metadata Management: Discover best practices for handling issue metadata separately.
  • Use Case: When you need to report a bug or propose a new feature, use this Skill to ensure your issue is well-defined and easily understood by the development team.

Quick Start

Use the issue-writing skill to draft a new GitHub issue about improving the user onboarding flow.

Frequently Asked Questions about issue-writing

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

FAQPage Schema
How do I write a structured GitHub issue for a bug report or feature request?▼

To write a structured GitHub issue, you need clear titles, precise problem statements, actionable acceptance criteria, and proper body content formatting. This ensures effective communication and faster development alignment within your workflows.

What is the best way to create GitHub issues via the command line without character escaping issues?▼

The best way to create GitHub issues via the command line is using heredoc formatting conventions. This approach avoids character escaping issues and ensures reliable issue submission directly from your CLI environment.

How should I handle issue metadata when submitting bug reports through the GitHub CLI?▼

You should handle issue metadata separately from the main body content when submitting bug reports. Managing metadata independently ensures the problem statement and acceptance criteria remain clear and easily parsed by development teams.

Does this approach to issue writing work for both bug reports and feature requests?▼

Yes, this issue writing approach works for both bug reports and feature requests. It guides the creation of well-defined titles and body content, ensuring your proposed features or reported bugs are easily understood by the development team.

What should be included in GitHub issue acceptance criteria to ensure faster development?▼

Acceptance criteria in GitHub issues should include actionable and precise desired outcomes. Defining these criteria clearly within the issue body facilitates effective communication and ensures better project alignment for faster development.

Related Skills

Explore More Product & Management Skills→
andrewthetechieandrewthetechie
2

request-to-prd

Transform bug reports and feature requests into structured first-draft PRDs with repo-aware context.

Community
Advanced
Kushal9889Kushal9889

fix-github-issue

Analyze GitHub issues, search code, implement fixes, and run tests.

Community
Intermediate
ClementWalterClementWalter
2

GitHub Workflow

Guide GitHub issue workflow with hierarchy, milestones, and automation scripts.

Community
Intermediate
hoonsubinhoonsubin

breakdown-plan

Generate GitHub issues from Epic, Feature, Story, Enabler, and Test hierarchies.

Community
Advanced