phase-fails

Name: phase-fails
Availability: InStock
Author: stanislavjiricek

Captures user complaints about plugins and categorizes them as core, science, or UX issues for GitHub reports.

6|Updated Mar 8, 2026

Search Tags:#feedback #error logging #issue tracking #bug report #github issues #user dissatisfaction

Ready to run

npx skills add https://github.com/stanislavjiricek/neuroflow --skill phase-fails

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: phase-fails
Source: https://github.com/stanislavjiricek/neuroflow/tree/main/skills/phase-fails
Command: npx skills add https://github.com/stanislavjiricek/neuroflow --skill phase-fails

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured way to capture, categorize, and report user dissatisfaction with the neuroflow plugin, streamlining the feedback process.

Core Features & Use Cases

Dissatisfaction Capture: Listens to user complaints without interruption.
Accurate Categorization: Routes issues to predefined categories (core, science, UX).
GitHub Issue Reporting: Facilitates easy creation of GitHub issues for tracked problems.
Use Case: A user reports that a generated analysis contains a statistical error. This Skill will categorize it as a 'science' issue and offer to create a GitHub issue for the developers.

Quick Start

Use the phase-fails skill to log a user complaint about a confusing prompt.

Frequently Asked Questions about phase-fails

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

FAQPage Schema

How do I log user dissatisfaction with plugin behavior and generate bug reports?▼

To log user dissatisfaction, you can capture complaints and categorize them into core, science, or UX domains. This process structures the feedback and prepares it for GitHub issue reporting to track problems upstream.

How do I categorize user feedback for issue tracking and bug reporting?▼

User feedback is categorized into core, science, or UX domains. This accurate categorization routes issues to predefined areas, streamlining the bug report process and ensuring upstream developers receive properly structured GitHub issues.

Can I automatically create a GitHub issue from a user complaint about scientific output quality?▼

Yes, you can create a GitHub issue from a user complaint about scientific output quality. The skill categorizes it as a 'science' issue and facilitates the generation of a GitHub issue report for upstream feedback.

What is the best way to track UX complaints for a software plugin?▼

The best way to track UX complaints is to capture the user's interaction experience without interruption and categorize it under the UX domain. This accurately logs the problem and prepares a GitHub issue report for developers.

Does this feedback logging tool require predefined categories for error logging?▼

Yes, this feedback logging tool requires predefined categories for error logging. User dissatisfaction must be routed into one of three predefined domains: core, science, or UX, to facilitate accurate problem logging and reporting.

When should I not use automated issue reporting for user dissatisfaction?▼

You should not use automated issue reporting when a user complaint lacks clear categorization. If dissatisfaction cannot be distinctly routed into core, science, or UX domains, the generated GitHub issue may lack accurate problem context.