skills.rest
tyevans
tyevansCOMMUNITY
Explore all skills by this author →
GitHub

bug

Create structured bug reports with reproduction steps and severity.

14|6|Updated Feb 3, 2026
Search Tags:#issue#report#tracking#bug#filing#defect
One-click install
npx skills add https://github.com/tyevans/tackline --skill bug-tyevans
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug
Source: https://github.com/tyevans/tackline/tree/main/skills/workflows/bug
Command: npx skills add https://github.com/tyevans/tackline --skill bug-tyevans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of reporting software defects by creating structured, actionable bug reports from descriptions or prior analysis outputs.

Core Features & Use Cases

  • Automated Bug Filing: Generates detailed bug reports with reproduction steps, severity, and affected artifacts.
  • Input Flexibility: Accepts direct descriptions or processes output from other skills like /critique or /review.
  • Use Case: After identifying a critical flaw in the user authentication module during a code review, use this skill to quickly file a detailed bug report, ensuring all necessary information for developers is captured.

Quick Start

Use the bug skill to file a bug report about the login button not working.

Frequently Asked Questions about bug

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

FAQPage Schema
How do I file a structured bug report from a software defect description?▼

To file a structured bug report, provide a description or prior analysis output. The skill identifies the artifact, symptom, reproduction steps, expected behavior, and severity, then confirms with you before filing the defect into a task tracker.

Can I submit a bug report directly from code review analysis?▼

Yes, you can submit a bug report directly from code review analysis. The skill accepts input from other analysis outputs like critique or review, converting those findings into structured, actionable defect tasks automatically.

What information is needed to track a software defect effectively?▼

To track a software defect effectively, you need the affected artifact, observed symptom, reproduction steps, expected behavior, and severity level. This skill extracts these details from your input to generate an actionable task for developers.

Does the bug filing process confirm details before submitting to a task tracker?▼

Yes, the bug filing process confirms details with you before submitting to a task tracker. It generates a structured report containing reproduction steps and severity, ensuring all necessary information is captured and verified prior to filing.

How do I handle broken software modules and report the issue?▼

To handle broken software modules, describe the issue or use prior analysis. The skill processes the description of the broken behavior, identifies the artifact and symptoms, and structures the information into a report ready for task tracking.

When should I use an automated bug report generator?▼

You should use an automated bug report generator when you need to streamline reporting software defects. It is ideal for converting identified flaws, such as a critical authentication module issue, into detailed reports ensuring all necessary developer information is captured.

Related Skills

Explore More Software Engineering Skills→
johnatas-henriquejohnatas-henrique

bug-report

Generate structured bug reports from user descriptions or static code analysis.

Community
Advanced
Cogni-DAOCogni-DAO

bug

Investigate software bugs and file structured bug reports.

Official
Intermediate
NodeJSmithNodeJSmith
1

mine.challenge

Critique code designs using three adversarial reviewer personas.

Community
Advanced
Haohao-endHaohao-end
779

qa-only

Produce report-only QA evidence with reproduction steps and screenshots.

Community
Basic