fsd:diagnose

Diagnose bugs and performance regressions in the @flow-state-dev repository.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/fixpoint-labs/flow-state-dev --skill fsd-diagnose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fsd:diagnose
Source: https://github.com/fixpoint-labs/flow-state-dev/tree/main/.agents/skills/diagnose
Command: npx skills add https://github.com/fixpoint-labs/flow-state-dev --skill fsd-diagnose

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured approach to diagnose and resolve hard bugs and performance regressions in the @flow-state-dev repository, ensuring efficient and effective debugging.

Core Features & Use Cases

  • Structured Diagnosis Loop: Offers a disciplined process for reproducing, minimizing, hypothesizing, instrumenting, fixing, and regression-testing bugs.
  • Reproducible Feedback Loops: Builds fast, deterministic feedback loops for identifying the root cause of issues.
  • Use Case: When a user reports a bug or performance issue, this Skill guides you through the process of diagnosing and resolving the problem.

Quick Start

Use the fsd:diagnose skill to initiate a diagnosis loop for a reported bug in the @flow-state-dev repository.

Frequently Asked Questions about fsd:diagnose

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

FAQPage Schema
How do I diagnose a hard bug in the flow-state-dev repository?

To diagnose a hard bug in the flow-state-dev repository, use a structured diagnosis loop that reproduces, minimizes, hypothesizes, instruments, fixes, and regression-tests the issue. This approach builds fast, deterministic feedback loops to identify the root cause efficiently.

What is the best way to resolve a performance regression in a pnpm project?

Resolving a performance regression in a pnpm project requires building reproducible feedback loops and using targeted debugging tools. A structured approach minimizes the regression, instruments the code to isolate the bottleneck, and applies regression testing to verify the fix.

Do I need specific debugging tools to diagnose bugs with this structured approach?

Yes, diagnosing bugs with this structured approach requires access to the repository and specific debugging tools like pnpm, fsdev, and various documentation files to establish reproducible feedback loops and targeted instrumentation.

How does a structured diagnosis loop help fix reproducible bugs?

A structured diagnosis loop helps fix reproducible bugs by enforcing a disciplined process of reproducing, hypothesizing, and instrumenting the code. This minimizes the bug scope and creates deterministic feedback loops for targeted root cause analysis.

Can I use this bug diagnosis process for any codebase or just the flow-state-dev repository?

This bug diagnosis process is specifically designed for the flow-state-dev repository, utilizing its particular debugging tools like fsdev and pnpm to provide structured, reproducible feedback loops tailored to that environment.