feedback

Convert QA feedback into a concrete modification plan for UI components and interaction flows.

3|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/alpoxdev/claude-code --skill feedback-alpoxdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feedback
Source: https://github.com/alpoxdev/claude-code/tree/main/.claude/skills/feedback
Command: npx skills add https://github.com/alpoxdev/claude-code --skill feedback-alpoxdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates QA feedback into a structured, repeatable process for identifying and applying UI and code fixes, reducing manual triage and inconsistent implementations.

Core Features & Use Cases

  • QA-driven analysis: Assess feedback, determine affected files, and propose 2-3 concrete options with tradeoffs.
  • Batch and parallel execution: Coordinate changes across components and screens with a parallel implementation strategy.
  • Validation and consistency: Run build, lint, and visual checks to ensure uniform UX and code quality.

Quick Start

Use the feedback skill to process a QA comment such as "Buttons are too small on mobile and error messages vary across pages" and generate a coordinated plan.

Frequently Asked Questions about feedback

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

FAQPage Schema
How do I convert QA feedback into a structured UI modification plan?

To convert QA feedback into a UI modification plan, analyze the feedback scope, explore affected components, generate options with tradeoffs, and execute parallel code fixes before running validation checks.

How do I fix inconsistent UI components across multiple screens at once?

Fixing inconsistent UI components across screens requires a parallel execution strategy that targets shared styles and interaction flows, enabling batch updates and uniform UX validation across the entire project.

What is the best way to process UI error messages and styling issues from QA reports?

Processing UI styling issues from QA reports involves translating the feedback into an action-oriented workflow: scope analysis, exploration, option generation, parallel implementation, and automated build and lint verification.

Can I batch update interaction flows and styles based on QA testing comments?

Yes, you can batch update interaction flows and styles by assessing the QA feedback to determine affected files, proposing concrete options, and coordinating parallel implementation across the targeted UI components.

Does this UI feedback workflow require specific dependencies to run build and lint checks?

No specific dependencies are required to run build and lint checks within this UI feedback workflow, as it operates independently to validate code quality and ensure visual consistency after applying modifications.

What are the limitations of using an automated workflow for UI refactoring from QA feedback?

The limitation of using an automated workflow for UI refactoring is that it requires a strictly structured process of scope analysis, option generation, and parallel implementation to accurately translate QA feedback without inconsistent manual triage.