bug-report

Convert UI anomalies into labeled GitHub issues with metadata.

1|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/Sn005/recommend-scp --skill bug-report-sn005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/Sn005/recommend-scp/tree/main/.claude/skills/bug-report
Command: npx skills add https://github.com/Sn005/recommend-scp --skill bug-report-sn005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automatically records UI exploration anomalies as GitHub issues, ensuring consistent tracking and labeling.

Core Features & Use Cases

  • Automatic issue creation: Converts subjective UI impressions into reproducible issues.
  • Smart labeling: Auto-assigns priority, screen, state, and type based on comparison with mocks/tokens/ACs.
  • Cloud fallback templates: When gh CLI unavailable, outputs a ready-to-submit template.

Quick Start

Describe the UI anomaly concisely to trigger an automatic bug report.

Frequently Asked Questions about bug-report

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

FAQPage Schema
How do I automatically create GitHub issues for UI anomalies found during exploration?

You can automatically create GitHub issues for UI anomalies by describing the anomaly concisely, which triggers the skill to convert subjective UI impressions into reproducible issues with automated labeling.

How does automated labeling work for UI bug reports on GitHub?

Automated labeling for UI bug reports works by comparing detected anomalies against mocks, tokens, and acceptance criteria, then auto-assigning priority, screen, state, and type labels to the GitHub issue.

Can I file GitHub bug reports without having the gh CLI installed?

Yes, you can file GitHub bug reports without the gh CLI; when the CLI is unavailable, the skill outputs a ready-to-submit cloud fallback template containing the required issue metadata.

What is the best way to track UI exploration anomalies across web and mobile interfaces?

The best way to track UI exploration anomalies across web and mobile interfaces is to use a skill that maps screens and components, detects anomalies, and creates GitHub issues with deterministic metadata.

Do I need to provide screen or component mappings to generate automated GitHub issues?

Yes, you need to provide screen and component mapping to generate automated GitHub issues, as this mapping provides the context required to apply deterministic steps for issue creation, labeling, and referencing.