Define and guide creation of X-Fidelity analysis rules with JSON and archetypes.
npx skills add https://github.com/zotoio/x-fidelity --skill xfi-create-rule
Please help me install this Agent Skill. Skill: xfi-create-rule Source: https://github.com/zotoio/x-fidelity/tree/main/.cursor/skills/xfi-create-rule Command: npx skills add https://github.com/zotoio/x-fidelity --skill xfi-create-rule
This Skill provides a structured, end-to-end guide for creating new X-Fidelity analysis rules, enabling teams to formalize rule purpose, required data, and implementation steps to ensure consistent governance across repositories.
Create and implement a new X-Fidelity rule by defining its purpose, selecting the appropriate facts and operators, drafting the rule JSON, adding it to an archetype, and validating it with tests.
High-intent search queries and answers about installing and using this skill.
To create static analysis rules, define the rule purpose, select necessary facts and operators, draft the JSON rule definitions, and integrate them with archetypes for testing and validation.
X-Fidelity rule development involves defining the rule's purpose, selecting appropriate facts and operators, drafting the JSON rule structure, adding it to an archetype, and validating its behavior through CLI or config server tests.
Testing custom rules with archetypes requires plugging the newly drafted JSON rules into the archetype configuration, running the validation tests, and verifying the expected behavior through the CLI or config server.
Building a static analysis rule requires selecting specific facts and operators that match your rule's defined purpose, which are then combined within the JSON rule structure to enforce code quality governance.
Validating new JSON rules without full deployment is possible by running targeted tests locally through the CLI or config server to verify the rule behavior against integrated archetypes.
Formalizing code quality checks into structured JSON rules is necessary when teams need consistent governance across multiple repositories, requiring defined rule purposes and standardized facts and operators.
Nickalus12Identify performance hotspots and regressions in Loom-style codebases.
bahayonghangSearch and validate code patterns using Tree-sitter structural queries.
faisalanjumTest model field enforcement by querying the AI's identity.
pax-kEnforce and document architecture boundaries using dependency-cruiser, ESLint, import-linter, and custom scripts.
