Skip to content
xtarter
Blog

The conformance CLI for JavaScript and TypeScript

It detects your stack, audits your configs, and plans every change. Nothing is written until you approve the plan.

Conform your projectView CLI Reference
pnpx xtarterize@latest check
Conformance audit
✗ Biome (lint + format) new
✔ tsconfig - strict compiler options skip
✔ tsconfig - path aliases skip
~ tsconfig - incremental: true patch
~ vite-plugin-checker patch
✗ Git hooks (commit-msg, …) new
✗ AGENTS.md new
…and 15 more tasks
2/22 conformant
The everyday loop: audit, preview, apply one task, roll back. Recorded against a Vite + React fixture with xtarterize 2.0.4; output trimmed.

How a run works

Every run follows the same five steps.

  1. Detect

    Profile the project: framework, bundler, package manager, existing configs.

  2. Resolve

    Map the profile to the conformance tasks that apply.

  3. Check

    Compare each file against the standard: new, patch, skip, or conflict.

  4. Plan

    Review the plan before anything is written.

  5. Apply

    Back up originals, then merge or rewrite configs.

Nothing moves without you

Preview every change, back up originals, and write only after you approve.

  • Preview the plan

    Run init or sync with --dry-run to preview every planned change; `.gitignore` may be created or updated, but no conformance files are written.

  • Backups by default

    Modified files are copied to .xtarterize/backups/ first. Undo and restore are built in.

  • You approve writes

    init asks before it applies, and conflicts surface instead of overwriting your configs.

What it can manage

Apply the whole set with init, or exactly one task with add. Everything else stays untouched.

Quick start

Three commands cover the loop.

Initialize conformance
npx xtarterize@latest init
Check conformance
npx xtarterize@latest check
Preview changes
npx xtarterize@latest diff

Starting from scratch?

create-xtarter-app scaffolds new projects on this same baseline.

Start with a templateStar on GitHub