xfi-debug-analysis

Diagnose X-Fidelity analysis failures across CLI and VSCode extension workflows.

1|1|Updated Dec 20, 2023
One-click install
npx skills add https://github.com/zotoio/x-fidelity --skill xfi-debug-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xfi-debug-analysis
Source: https://github.com/zotoio/x-fidelity/tree/main/.cursor/skills/xfi-debug-analysis
Command: npx skills add https://github.com/zotoio/x-fidelity --skill xfi-debug-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging X-Fidelity analysis issues and failures to help engineers quickly identify the root causes across CLI and VSCode extension contexts.

Core Features & Use Cases

  • Guided diagnostic checklist for archetype detection, inclusion patterns, and rule evaluation
  • Comprehensive logging with configurable levels and outputs for CLI and VSCode extension
  • VSCode extension debugging aids, control center status visibility, and unified diagnostics across tools

Quick Start

Run xfi --debug in your workspace and review the Output panels to locate the failure.

Frequently Asked Questions about xfi-debug-analysis

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

FAQPage Schema
How do I debug X-Fidelity analysis issues in VSCode?

To debug X-Fidelity analysis issues in VSCode, run `xfi --debug` in your workspace and review the Output panels to locate the failure. The extension provides control center status visibility and unified diagnostics across tools.

What is the best way to diagnose archetype detection failures during analysis?

The best way to diagnose archetype detection failures is to use a guided diagnostic checklist that evaluates file inclusion patterns and rule evaluation. This approach provides structured diagnostics and detailed logs for reproducible troubleshooting.

Can I use command line tools to troubleshoot X-Fidelity extension diagnostics?

Yes, you can use command line tools to troubleshoot X-Fidelity extension diagnostics. The diagnostic workflow is applicable to both CLI and VSCode extension contexts, providing comprehensive logging with configurable levels and outputs.

Why does rule evaluation not work when analyzing my workspace?

Rule evaluation may not work due to incorrect archetype detection or file inclusion patterns. Use the guided diagnostic checklist to identify the root cause, and review detailed logs with configurable levels to trace the failure.

How do I get reproducible troubleshooting logs for X-Fidelity analysis?

You get reproducible troubleshooting logs for X-Fidelity analysis by using environment controls and configurable logging levels. Run the diagnostics in your workspace to generate structured outputs that help pinpoint the root cause.