feedback

Capture software feedback and route it to GitHub issues and project backlogs.

45|2|Updated Apr 24, 2026

Search Tags:#feedback #github #triage #issue-management #bug-tracking #product-backlog

Ready to run

npx skills add https://github.com/hachej/boring-ui --skill feedback-hachej

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feedback
Source: https://github.com/hachej/boring-ui/tree/main/.agents/skills/feedback
Command: npx skills add https://github.com/hachej/boring-ui --skill feedback-hachej

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of disorganized and incomplete feedback collection by providing a structured, canonical process for capturing bugs and feature ideas.

Core Features & Use Cases

Canonical Issue Capture: Ensures every report includes impact, observed behavior, and environment details.
Automated Routing: Integrates with GitHub issues and project backlogs to keep feedback actionable.
Use Case: When a user encounters a bug, this skill guides the agent to redact sensitive data, search existing issues for duplicates, and create a properly labeled GitHub issue.

Quick Start

Ask the agent to capture the current bug report and route it to the appropriate project board.

Frequently Asked Questions about feedback

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

FAQPage Schema

How do I organize software feedback into GitHub issues?▼

Capturing software feedback into GitHub issues requires a structured triage process that standardizes bug reports and feature requests. This approach ensures every entry includes impact, observed behavior, and environment details before routing it to a project backlog.

What is the best way to prevent duplicate bug reports in a product backlog?▼

Preventing duplicate bug reports in a product backlog involves using a multi-step verification process. This approach searches existing issues for duplicates and enforces adherence to documented issue templates before creating a new entry.

How can I redact sensitive data when capturing bug tracking reports?▼

When capturing bug tracking reports, sensitive data is redacted during the issue creation workflow. The process guides the agent to sanitize inputs before submitting the standardized report to GitHub issues or project backlogs.

Does this issue management approach work with existing project management workflows?▼

Yes, this issue management approach integrates with existing project management workflows. It requires adherence to your documented issue templates and current processes to ensure data quality and prevent duplication across your project boards.

When should I use a structured triage process for feature requests?▼

A structured triage process for feature requests is needed when you require canonical issue capture. This ensures every feature idea includes necessary impact and environment details, keeping your feedback actionable and organized.