analyzing-feedback

Transform raw customer feedback into severity-ranked themes with codebase impact.

7|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Agent-Engineer-Master/skill-engineer --skill analyzing-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyzing-feedback
Source: https://github.com/Agent-Engineer-Master/skill-engineer/tree/main/product/analyzing-feedback
Command: npx skills add https://github.com/Agent-Engineer-Master/skill-engineer --skill analyzing-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Parses raw customer feedback (app reviews, support tickets, interview transcripts) into categorized severity-ranked themes, scans the codebase to identify affected files and components, and proposes 3 structural edit options per theme (minimal/refactor/architectural) with rationale tied directly to the original feedback. Trigger when: user provides raw customer feedback and wants to know what to change in the code; or an agent holds user complaints needing file-level engineering proposals. Do NOT trigger for: internal PR/code review comments (use receiving-code-review instead), stack-trace bug reports (use systematic-debugging instead), or PRD drafting.

Core Features & Use Cases

  • Ingest feedback and extract concrete behaviours to drive structured themes
  • Classify themes by category, severity, and pattern count, then map to relevant code areas
  • Propose exactly 3 edit options per theme with rationale tied to the original feedback
  • Gate via human confirmation and codebase-scanning rules to ensure safe, scoped changes

Quick Start

Paste raw customer feedback to generate themes and three edit options per theme.

Frequently Asked Questions about analyzing-feedback

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

FAQPage Schema
How do I turn raw customer feedback into actionable code changes?

To turn raw customer feedback into actionable code changes, ingest app reviews or support tickets to extract severity-ranked themes, scan the codebase for affected files, and generate three structural edit options per theme.

What is the best way to map user complaints to specific files in my codebase?

The best way to map user complaints to specific files is by scanning your repository to identify affected components, categorizing feedback into severity-ranked themes, and targeting exact code areas tied to the original issues.

Does this feedback analysis approach work with internal PR comments?

This feedback analysis approach does not work with internal PR comments; it is designed specifically for raw customer feedback like app reviews, support tickets, and interview transcripts.

How do I generate engineering proposals from app reviews and support tickets?

To generate engineering proposals from app reviews and support tickets, parse the feedback into categorized themes, map them to relevant code areas, and propose three edit options per theme with human-gated validation.

What types of edit options are proposed for each feedback theme?

For each feedback theme, three structural edit options are proposed: minimal, refactor, and architectural, each providing a distinct scope of code change with rationale tied directly to the original feedback.