skills.rest
nntan90
nntan90COMMUNITY
Explore all skills by this author →
GitHub

bug-report

Generate standardized bug reports for Jira, GitHub Issues, and Linear.

4|1|Updated Mar 24, 2026
Search Tags:#templates#linear#jira#reproduce#bug-reporting#github-issues#bug-report
One-click install
npx skills add https://github.com/nntan90/qa-skill-suite --skill bug-report-nntan90
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/nntan90/qa-skill-suite/tree/main/bug-report
Command: npx skills add https://github.com/nntan90/qa-skill-suite --skill bug-report-nntan90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create structured, reproducible bug reports to speed triage and ensure consistent documentation of defects across teams.

Core Features & Use Cases

  • Structured bug reports with sections for observed vs. expected behavior, steps to reproduce, environment, severity, and evidence
  • Templates for Jira, GitHub Issues, and Linear to streamline ticket creation
  • Trigger phrases to load the skill and draft tickets from natural language requests

Quick Start

Provide a complete bug report by outlining observed behavior, steps to reproduce, environment, and evidence, then request a Jira/GitHub/Linear template to generate a ticket.

Frequently Asked Questions about bug-report

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

FAQPage Schema
How do I create a reproducible bug report for Jira, GitHub Issues, or Linear?▼

To create a reproducible bug report, document the observed behavior, exact steps to reproduce, environment details, severity, and evidence. Using standardized templates for Jira, GitHub Issues, or Linear ensures consistent ticket creation and speeds up triage.

What fields are required for a standardized bug report?▼

A standardized bug report requires observed behavior, steps to reproduce, environment, severity, and frequency fields. Enforcing these required fields ensures defects are documented consistently across teams and provides the necessary context for effective triage.

Can I draft bug reports from natural language requests?▼

Yes, you can draft bug reports from natural language requests by using trigger phrases to load the skill. Provided you supply the observed behavior, reproduction steps, environment, and evidence, the skill generates a structured ticket for your target platform.

What is the best way to document software defects for cross-platform triage?▼

The best way to document software defects for triage is using structured templates that compare observed versus expected behavior. Including environment details, severity, frequency, and evidence speeds up cross-platform ticket creation and ensures consistent documentation.

Why should I include evidence and environment details in bug tickets?▼

Including evidence and environment details in bug tickets provides the context needed to reproduce the software defect. Documenting these alongside observed behavior and reproduction steps ensures accurate triage and consistent defect tracking across teams.

Related Skills

Explore More Software Engineering Skills→
hpsgdhpsgd

write-bug-report

Generate structured bug reports from raw descriptions with mandatory sections.

Official
Advanced
lciaccilciacci

ticket-craft

Create self-contained software tickets with acceptance criteria and verification commands.

Community
Advanced
KIM-KYOUNG-OHKIM-KYOUNG-OH

issue-bug-report

Convert error logs and stack traces into structured Markdown bug reports.

Community
Advanced
burnt-labsburnt-labs
6

gitbook

Edit GitBook documentation locally with full syntax and configuration reference.

Official
Intermediate