skills.rest
Jose-Polanco-Oxte
Jose-Polanco-OxteCOMMUNITY
Explore all skills by this author →
GitHub

issues-writer

Generate structured Markdown issue reports for bug, feature, and technical debt tracking.

3|Updated Aug 8, 2026
Search Tags:#documentation#technical debt#issue tracking#bug report#github issues#jira#markdown templates
One-click install
npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill issues-writer-jose-polanco-oxte
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issues-writer
Source: https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer/tree/main/.agents/skills/issues-writer
Command: npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill issues-writer-jose-polanco-oxte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns unstructured bug reports, feature ideas, and technical debt notes into consistent, actionable issue documents with reproduction steps, acceptance criteria, and metadata, ready for trackers like GitHub Issues or Jira. ## Core Features & Use Cases - Issue Categorization: Classifies requests as bug, feature, task, or tech-debt and applies the matching template. - Standardized Templates: Provides Markdown templates covering metadata, reproduction steps, expected vs. actual results, and Definition of Done checklists. - File Output Convention: Saves finalized issues to a resources directory using a predictable issue-[type]-[slug].md naming scheme. - Use Case: A developer observes an intermittent CI failure and asks the assistant to log it; the skill produces a complete bug report with environment details, log excerpts, root cause analysis, and candidate fixes saved as a Markdown file. ## Quick Start Ask the assistant to write a bug report for the problem you observed, including steps to reproduce and expected behavior.

Frequently Asked Questions about issues-writer

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

FAQPage Schema
How do I write a structured bug report for GitHub Issues?▼

Provide the observed behavior, steps to reproduce, expected results, and environment details. The skill categorizes it as a bug, populates the bug template with metadata and log excerpts, and saves the finished Markdown file to its resources directory.

How to document technical debt as an actionable ticket?▼

Describe the refactoring or infrastructure work needed and its rationale. The skill applies the task/tech-debt template, which captures the objective, proposed technical changes, and a Definition of Done checklist.

What issue types does this skill support?▼

It supports four classifications: bug for unexpected behavior or crashes, feature for new functionality requests, and task or tech-debt for refactoring, testing, and documentation work. Each type maps to a dedicated Markdown template.

Where are the generated issue files saved?▼

Finalized issues are written to the skill's resources directory using the naming pattern issue-[type]-[short-slug].md, for example issue-bug-auth-token-expiration.md. File system write access is required.

Does the skill validate issues before saving them?▼

No automated validator script is bundled. The instructions require manually checking required fields, reproduction or acceptance criteria, links, and placeholder consistency against the selected template before saving.

Related Skills

Explore More Software Engineering Skills→
Oz-NetworksOz-Networks
6

mirra-feedback

Report bugs, feedback, and feature requests through a REST API.

Official
Intermediate
Aum08DesaiAum08Desai

github-issues

Manage GitHub issues via gh CLI or REST API.

Community
Intermediate
jonkikyjonkiky

investigate

Trace reported issue symptoms to code paths and verify root cause hypotheses.

Community
Advanced
DaddyElonMusk69DaddyElonMusk69

github-issues

Manage GitHub issues via gh CLI or REST API.

Community
Intermediate