product-bug-report

Generates plain-language bug briefings and HTML reports from GitHub issue backlogs.

78|27|Updated May 4, 2024
One-click install
npx skills add https://github.com/fedixyz/fedi --skill product-bug-report-fedixyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-bug-report
Source: https://github.com/fedixyz/fedi/tree/main/.agents/skills/product-bug-report
Command: npx skills add https://github.com/fedixyz/fedi --skill product-bug-report-fedixyz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Product leads and non-technical stakeholders cannot read a raw GitHub backlog: it mixes internal engineering chores with real user-facing bugs and is written in jargon. This Skill turns the live issue backlog into a short, plain-language briefing of what is actually broken for users, plus a self-contained HTML report with status grouping. ## Core Features & Use Cases - Backlog triage and translation: Pulls the most recently active open issues via the GitHub CLI, filters out internal test, infra, and feature work, and rewrites surviving items as user-facing symptoms. - Dual-output rendering: A bundled Python script renders one JSON synthesis into both an inline chat briefing and a styled HTML report with status tiles, a by-status view, and expandable detail per item. - Self-audit loop: A shell script checks the rendered report for mechanical failures (external assets, oversized pages, missing issue links, sideways scroll) and captures light, dark, narrow, and by-status screenshots for visual review. - Use Case: A founder asks "what are users complaining about right now?" The Skill fetches the latest backlog activity, curates at most 10 felt problems, and delivers a ranked briefing plus a shareable visual report. ## Quick Start Ask the assistant to summarize what is currently broken for users in the app and produce a bug report from the GitHub backlog.

Frequently Asked Questions about product-bug-report

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

FAQPage Schema
How do I create a bug report from GitHub issues for non-technical stakeholders?

Fetch the most recently active open issues with the GitHub CLI, filter out internal engineering work, rewrite each surviving item as a user-facing symptom, and render the result as a short briefing plus an HTML report. This Skill automates that full pipeline from one JSON file.

How does the skill decide which GitHub issues are user-facing bugs?

It applies one test: would a person who only uses the app notice or care about this. Internal test automation, feature construction, developer tooling, and ops chores are dropped, while crashes, stuck funds, chat problems, and broken screens are kept.

What tools are required to run this bug report workflow?

The workflow uses the GitHub CLI (gh) to list and view issues, Python 3 to render the JSON synthesis into HTML and markdown, and a bash script with headless Chrome to audit the rendered report and capture screenshots.

Can the HTML report group bugs by fix status?

Yes. The rendered page includes a by-status view with four buckets: Open, Being looked into, Fix in progress, and Done waiting on a release. Status values must match this vocabulary exactly or items fall into a neutral Other bucket with a stderr warning.

Why does the report limit the list to ten items?

The output is a briefing, not an inventory. Capping at ten items forces curation toward what is recently active and what hurts users most, which is what a product reader actually needs from a backlog of over a thousand issues.