skills.rest
supertyrelle
supertyrelleCOMMUNITY
Explore all skills by this author →
GitHub

bug

Extract artifact, symptom, repro steps, expected behavior, and severity into structured bug reports.

Updated Feb 20, 2026
Search Tags:#code review#beads#issue tracking#bug#defect triage#repro steps
One-click install
npx skills add https://github.com/supertyrelle/pelley --skill bug-supertyrelle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug
Source: https://github.com/supertyrelle/pelley/tree/main/skills/bug
Command: npx skills add https://github.com/supertyrelle/pelley --skill bug-supertyrelle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The bug skill turns a defect description, review output, or conversation context into a structured bug report that can be tracked in the beads backlog without losing important details.

Core Features & Use Cases

  • Defect Extraction: Identifies the affected artifact, symptom, repro steps, expected behavior, and severity from direct input or upstream pipe-format output.
  • Triage and Confirmation: Asks for clarification when details are ambiguous and confirms the report before creating any issue.
  • Backlog Filing: Creates a well-scoped bug item with provenance so findings from /critique or /review become actionable work.
  • Use Case: After a code review uncovers a broken edge case, use this skill to convert the finding into a prioritized bug with clear reproduction steps.

Quick Start

Tell the bug skill to file a structured bug report from the issue description or review findings you want tracked.

Frequently Asked Questions about bug

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

FAQPage Schema
How do I convert code review findings into structured bug reports?▼

Converting code review findings into structured bug reports involves extracting the affected artifact, symptom, repro steps, expected behavior, and severity from pipe-format review output or direct defect descriptions to file a tracked issue.

What information is required for defect triage when filing a bug report?▼

Defect triage requires the affected artifact, symptom, repro steps, expected behavior, and severity. The skill asks for clarification when these details are ambiguous before creating any backlog item.

Can I use conversational findings from a critique to create actionable backlog tasks?▼

Yes, conversational findings from a critique can be turned into actionable backlog tasks. The skill processes direct input or upstream pipe-format output to create well-scoped bug items with provenance for tracking.

Does the bug filing process confirm the report before creating an issue in the backlog?▼

Yes, the bug filing process confirms the report before creating an issue in the backlog. It asks for clarification on ambiguous details and confirms the structured report to ensure findings become actionable work without losing important details.

What is the best way to track defects identified during backlog triage?▼

Tracking defects identified during backlog triage involves filing structured bug reports that include the artifact, symptom, repro steps, expected behavior, and severity, ensuring conversational findings are converted into actionable beads tasks with provenance.

Related Skills

Explore More Software Engineering Skills→
tyevanstyevans
14

bug

Create structured bug reports with reproduction steps and severity.

Community
Intermediate
opendatadiscoveryopendatadiscovery

triage

Convert raw scanner findings into categorized backlog work items.

Official
Advanced
tyevanstyevans
14

merge

Merge and deduplicate findings from conversation context, TaskList outputs, and SendMessage history.

Community
Intermediate
idchain-worldidchain-world
16

sarif-parsing

Parse SARIF 2.1.0 analysis results and deduplicate findings by fingerprint.

Official
Advanced