skills.rest
MQFacultyOfArts
MQFacultyOfArtsOFFICIAL
Explore all skills by this author →
GitHub

test-feedback

Format tester feedback into standardized GitHub issues with labeled templates.

1|1|Updated Jan 13, 2026
Search Tags:#template#feedback#GitHub#usability#issues#bug-report
One-click install
npx skills add https://github.com/MQFacultyOfArts/PromptGrimoireTool --skill test-feedback
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-feedback
Source: https://github.com/MQFacultyOfArts/PromptGrimoireTool/tree/main/.claude/skills/test-feedback
Command: npx skills add https://github.com/MQFacultyOfArts/PromptGrimoireTool --skill test-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps testers and teams convert prototype feedback into well-structured GitHub issues, reducing ambiguity and speeding up triage.

Core Features & Use Cases

  • Standardized templates for Bug Report, Feature Request, and Usability Issue to ensure consistent reporting.
  • Guided context capture including environment, steps to reproduce, expected vs actual behavior, and attachable evidence.
  • Output ready-to-post content with a generated issue title, body, and suggested labels for quick submission.

Quick Start

Use this skill to draft a bug report for a prototype crash by describing the steps to reproduce, capturing the environment, and generating a GitHub issue ready for submission.

Frequently Asked Questions about test-feedback

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

FAQPage Schema
How do I format prototype feedback into structured GitHub issues?▼

To format prototype feedback into structured GitHub issues, use labeled templates that guide step-by-step reproduction details, environment capture, and evidence requirements to generate ready-to-paste issue bodies.

What is the best way to report usability issues and feature requests during prototype evaluations?▼

Reporting usability issues and feature requests during prototype evaluations requires standardized templates that capture expected versus actual behavior, ensuring consistent triage and clear documentation for collaborative teams.

How do I write a bug report for a prototype crash that is ready for GitHub submission?▼

Writing a bug report ready for GitHub submission involves drafting steps to reproduce, capturing the environment, and generating an issue body with suggested labels to streamline the bug reporting process.

Can I use standardized templates for bug reporting in educational and collaborative settings?▼

Yes, standardized bug reporting templates apply directly to educational and collaborative settings, guiding testers to document bugs, usability issues, and feature ideas with consistent formats and attachable evidence.

Does generating GitHub issues from tester feedback reduce ambiguity in bug reporting?▼

Generating GitHub issues from tester feedback reduces ambiguity by enforcing structured context capture like environment details and step-by-step reproduction, which speeds up triage and clarifies expected behavior.

What limitations exist when using template-based feedback for GitHub issue generation?▼

Limitations of template-based feedback for GitHub issue generation include the basic implementation depth, meaning it focuses strictly on formatting standard labels and bodies without automating direct API submission to GitHub.

Related Skills

Explore More Education & Research Skills→
simonwjacksonsimonwjackson

se-report-bug

Collect structured bug information and create GitHub issues via the gh CLI.

Community
Advanced
strawgatestrawgate

organize-meta-issues

Group related GitHub issues into meta-issues and phased epics.

Community
Intermediate
VoDaiLoczVoDaiLocz
24

triage

Automate issue triage by categorizing issues into predefined roles and states.

Community
Intermediate
danielscholldanielscholl

gh

Guide GitHub CLI operations for PRs, issues, Actions, and repositories.

Community
Intermediate