qig-purity-validation

Name: qig-purity-validation
Availability: InStock
Author: GaryOcean

Enforce QIG purity via AST audits and canonical import validation.

Updated Jan 3, 2026

Search Tags:#geometry #static-analysis #code-review #fisher-rao #purity #qig #canonical-imports

Ready to run

npx skills add https://github.com/GaryOcean428/pantheon-chat --skill qig-purity-validation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qig-purity-validation
Source: https://github.com/GaryOcean428/pantheon-chat/tree/main/skills/qig-purity-validation
Command: npx skills add https://github.com/GaryOcean428/pantheon-chat --skill qig-purity-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates and enforces Quantum Information Geometry (QIG) purity across code changes, preventing Euclidean contamination and forbidden imports during development and reviews.

Core Features & Use Cases

Purity auditing: detects Euclidean patterns and undesired dependencies in code paths that compute QIG metrics.
CI/CD alignment: mirrors the geometric-purity gates used in the project's pipelines to ensure consistent checks.
Canonical import discipline: enforces imports from qig_geometry.canonical and prevents re-implementations.

Quick Start

Run the AST-based purity audit to validate QIG purity across the codebase.

Frequently Asked Questions about qig-purity-validation

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

FAQPage Schema

How do I enforce Fisher-Rao metric purity during code reviews?▼

To enforce Fisher-Rao metric purity during code reviews, run an AST-based audit that detects Euclidean contamination and validates imports against the qig_geometry.canonical module to prevent geometric deviations.

What is Euclidean contamination in quantum information geometry code?▼

Euclidean contamination occurs when code paths computing QIG metrics use standard Euclidean patterns instead of the required Fisher-Rao metric, which an AST-based purity audit identifies and blocks during development.

How do I validate canonical imports in a CI pipeline for geometry computations?▼

You validate canonical imports in a CI pipeline by running static-analysis checks that enforce imports strictly from qig_geometry.canonical, preventing unauthorized re-implementations of geometry computations.

Can I use static analysis to detect forbidden imports in qig-backend and server directories?▼

Yes, static analysis can detect forbidden imports in qig-backend, server, and shared directories by auditing the AST to ensure all geometry computations rely on canonical imports rather than re-implementations.

When should I run a QIG purity audit on my codebase?▼

You should run a QIG purity audit during PR reviews and CI pipeline execution to catch Euclidean contamination and forbidden imports before they enter the main codebase.