review-feedback

Name: review-feedback
Availability: InStock
Author: zillabunny

Triage exported feedback JSON and file GitHub issues via gh CLI.

Updated Apr 2, 2026

Search Tags:#automation #feedback #github #review #issues #triage

Ready to run

npx skills add https://github.com/zillabunny/GoblinVolleyball-1.1 --skill review-feedback-zillabunny

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-feedback
Source: https://github.com/zillabunny/GoblinVolleyball-1.1/tree/main/.claude/skills/review-feedback
Command: npx skills add https://github.com/zillabunny/GoblinVolleyball-1.1 --skill review-feedback-zillabunny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly triage and file actionable feedback from an in-app feedback panel, turning user reports into trackable GitHub issues.

Core Features & Use Cases

Triage feedback: Read exported feedback JSON and evaluate each pending entry for actionability.
Duplicate detection & labeling: Identify duplicates and assign appropriate labels (bug, enhancement, UI, question).
Automated filing via gh CLI: Create GitHub issues with structured bodies once approved and summarized.

Quick Start

Run the review-feedback workflow on feedback.json to triage and file approved entries as GitHub issues.

Frequently Asked Questions about review-feedback

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

FAQPage Schema

How do I automate triaging in-app feedback and creating GitHub issues?▼

Automating in-app feedback triage involves reading a feedback.json file, evaluating pending entries for actionability, detecting duplicates, assigning labels, and filing structured GitHub issues via the gh CLI. This workflow converts user reports into trackable items.

What is the best way to detect duplicate feedback before filing GitHub issues?▼

The best way to detect duplicate feedback is to process exported JSON entries through an automated triage workflow that checks pending items against existing reports, assigns appropriate labels, and prepares issue bodies for filing via the gh CLI.

Do I need a specific file format to automate GitHub issue filing from user feedback?▼

Yes, you need a feedback.json file placed at the repository root. This JSON format contains the exported in-app feedback entries required for the triage workflow to evaluate actionability and file issues via the gh CLI.

Can I assign labels like bug or enhancement automatically when filing GitHub issues?▼

Yes, automated triage workflows can assign labels such as bug, enhancement, UI, and question to feedback entries. This categorization happens during the evaluation phase before creating the structured issue body via the gh CLI.

Does this triage workflow support custom helper scripts for processing feedback?▼

Yes, the workflow interfaces with an optional local helper script located at scripts/review-feedback.js. If present, this script integrates with the core triage logic to process exported feedback entries before filing GitHub issues.

When should I not use an automated workflow for feedback triage and issue filing?▼

You should avoid automated feedback triage if your user reports are not exported as a feedback.json file or if you lack gh CLI configured for controlled workflow access, as the automation depends on these specific inputs to function correctly.