lina-feedback

Triage user feedback on LinaPro implementations and manage fixes via OpenSpec workflows.

147|28|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/linaproai/linapro --skill lina-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lina-feedback
Source: https://github.com/linaproai/linapro/tree/main/.agents/skills/lina-feedback
Command: npx skills add https://github.com/linaproai/linapro --skill lina-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of handling user feedback on existing LinaPro implementations (including bugs, defects, improvements, suggestions, and missing features) in an ad-hoc, untraceable way, ensuring all feedback is properly triaged, fixed, validated, and tracked according to OpenSpec workflows when applicable.

Core Features & Use Cases

  • Intelligent Feedback Triage: Automatically classifies feedback into four processing paths (append to active OpenSpec change, create new OpenSpec change, direct fix, or no change) based on impact scope, long-term value, and OpenSpec record thresholds.
  • End-to-End Fix Workflow: Performs root cause analysis, implements minimal focused fixes, runs required unit/E2E tests, and conducts full impact analysis for all processed feedback.
  • OpenSpec Integration: Seamlessly links feedback to existing or new OpenSpec changes, updates incremental specifications for spec-level issues, and maintains traceable task tracking for all OpenSpec-aligned changes.
  • Use Case: When a user reports a bug in the menu management module that causes circular references in the parent selector, this Skill triages the feedback to the relevant active OpenSpec change, implements the fix, runs all related regression tests, and updates the task list to mark the issue as resolved.

Quick Start

Use the lina-feedback skill to process the user-reported menu parent selector circular reference bug, including triage, implementation, and test validation.

Frequently Asked Questions about lina-feedback

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

FAQPage Schema
How do I triage user feedback and bug reports for existing full-stack implementations?

Feedback triage categorizes user reports into four processing paths: appending to active changes, creating new changes, direct fixes, or no change. This classification is based on impact scope, long-term value, and change management thresholds to ensure traceable handling of bugs and missing features.

What is the best way to handle post-implementation bug fixes with traceable change tracking?

Traceable bug fixes are handled by performing root cause analysis, implementing minimal focused fixes, and running regression tests. The workflow links feedback to active or new change records to maintain end-to-end traceability throughout the closure process.

How does feedback triage integrate with OpenSpec change management workflows?

OpenSpec integration links user feedback directly to existing or new changes, updates incremental specifications for spec-level issues, and maintains task tracking. This ensures all modifications align with established change management protocols for full-stack projects.

Can I use this workflow for regression testing and test validation after a defect fix?

Test validation is a core component of the fix workflow. After implementing a defect fix, the system runs required unit and E2E tests, conducts full impact analysis, and updates task lists to mark the regression testing phase as resolved.

When should I create a new OpenSpec change versus appending to an active one?

Creating a new change is triggered when feedback scope or long-term value exceeds established thresholds. Conversely, appending to an active change occurs when the reported issue falls within the existing impact scope of an ongoing modification.

Does feedback triage support missing features and improvement suggestions or only defect fixes?

Feedback triage supports missing features and improvement suggestions alongside defect fixes. It evaluates all incoming user feedback against impact scope and long-term value to determine the appropriate processing path for any type of input.