xfi-consistency-testing

Validate parity between X-Fidelity CLI and VSCode extension analysis results.

1|1|Updated Dec 20, 2023

Search Tags:#testing #vscode #consistency #integration #cli #diffing

Ready to run

npx skills add https://github.com/zotoio/x-fidelity --skill xfi-consistency-testing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: xfi-consistency-testing
Source: https://github.com/zotoio/x-fidelity/tree/main/.cursor/skills/xfi-consistency-testing
Command: npx skills add https://github.com/zotoio/x-fidelity --skill xfi-consistency-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and ensure parity between the X-Fidelity CLI and VSCode extension analyses, so results, locations, and severities are consistent across tools.

Core Features & Use Cases

Validate identical issue counts, file paths, and severities between CLI and VSCode extension analyses.
Support integration and pre-release checks using a known fixtures workspace to catch drift early.
Aid debugging by surfacing where discrepancies originate and guiding fixes across archetypes and rules.

Quick Start

Run a consistency check against a known fixtures workspace to verify parity between CLI and VSCode extension results.

Frequently Asked Questions about xfi-consistency-testing

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

FAQPage Schema

How do I keep CLI and VSCode extension analysis results consistent?▼

To keep CLI and VSCode extension analysis results consistent, run a consistency check against a known fixtures workspace to validate identical issue counts, file paths, and severities, catching any drift before release.

What is CLI and VSCode extension analysis parity testing?▼

CLI and VSCode extension analysis parity testing verifies that both tools use identical archetypes, rules, and issue reporting with deterministic locations and severities, ensuring reliable cross-tool debugging and seamless integration.

Why does my VSCode extension show different analysis results than the CLI?▼

Different VSCode extension and CLI analysis results indicate a parity drift between archetypes or rules; running a consistency check against a fixtures workspace surfaces exactly where discrepancies originate to guide fixes.

Can I use fixtures workspaces for pre-release consistency verification?▼

Yes, you can use a known fixtures workspace for pre-release consistency verification to validate identical issue counts, file paths, and severities between the CLI and VSCode extension, catching integration drift early.

How do I debug discrepancies between CLI and VSCode extension analysis?▼

To debug discrepancies between CLI and VSCode extension analysis, run a consistency check to surface where the drift originates across archetypes and rules, then apply fixes to restore deterministic issue reporting.

Do I need identical archetypes and rules for CLI and VSCode testing?▼

Yes, you need identical archetypes and rules for CLI and VSCode testing to enforce parity, ensuring both tools report issues with deterministic locations and severities for reliable cross-tool debugging.