conform

Detect schema drift in blitz runtime artifacts and plugin structures.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/lasswellt/blitz-cc --skill conform-lasswellt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conform
Source: https://github.com/lasswellt/blitz-cc/tree/main/skills/conform
Command: npx skills add https://github.com/lasswellt/blitz-cc --skill conform-lasswellt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill resolves schema drift in blitz runtime artifacts and plugin structures that occurs after plugin upgrades or when working with forked blitz repositories, preventing broken sprint workflows, failed quality gates, and invalid critic validation.

Core Features & Use Cases

  • Multi-Scope Auditing: Scans project artifacts (sessions, sprints, stories, roadmap, research docs) and plugin structures (skill frontmatter, hooks, companion files) for schema drift, with support for project, plugin, and full sweep scopes.
  • Safe, Idempotent Migration: Runs read-only by default; use --fix to apply additive migrations that preserve all canonical field names and project-specific extensions, with automatic backups and per-file error isolation.
  • Common Use Case: After upgrading the blitz plugin, run conform to automatically add missing registry_entries to all sprint stories, normalize malformed activity-feed entries, and clean up orphan session locks without manual data entry.

Quick Start

Invoke the conform skill with the --fix flag to automatically migrate all non-conformant blitz artifacts in your current project directory to match the current canonical schema.

Frequently Asked Questions about conform

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

FAQPage Schema
How do I detect schema drift in blitz artifacts after a plugin upgrade?

Schema drift in blitz artifacts is detected by probing artifact versions and validating frontmatter and hook wiring against canonical schemas. The conform skill scans project and plugin scopes to identify non-conformant fields before they cause sprint workflow failures.

What is the safest way to migrate blitz sprint stories to a new schema?

The safest schema migration method is an idempotent, additive-only process that preserves canonical field names and project-specific extensions. Running conform with the --fix flag applies these migrations automatically while creating backups and isolating per-file errors.

Does the conform schema migration tool work with standard Vue and Nuxt projects?

Schema migration with conform applies exclusively to blitz-powered Vue/Nuxt and Firebase projects, including forked plugin repositories. It does not support standard Vue and Nuxt projects lacking the blitz runtime artifact structure.

Can I audit blitz plugin frontmatter without applying changes to the files?

Yes, you can audit blitz plugin frontmatter and hooks without applying changes. Conform operates read-only by default, reporting schema drift across project, plugin, and full sweep scopes without mutating any files.

Why do failed quality gates occur in forked blitz repositories?

Failed quality gates in forked blitz repositories occur due to schema drift in runtime artifacts and plugin structures. Validating artifact versions and normalizing malformed activity-feed entries resolves the invalid critic validation causing these failures.