CodeCharter.Cli 1.6.3

CodeCharter CLI

Deterministic code quality analysis for .NET, built on Roslyn. Write rules in a LINQ-like DSL, store them as .ccr files, and run them from the command line, in CI, or from your editor.

Installed as a .NET global tool, the command is codecharter:

dotnet tool install --global CodeCharter.Cli
codecharter analyze MyProject.sln --rules path/to/rules

What it does

• analyze — analyze a solution or project and report findings, with CI-friendly exit codes and a --git-ref mode that gates only changed lines.
• validate / test / docs — parse and type-check a .ccr rule, run its spec (hit/miss cases), and read the rule-authoring documentation offline.
• restore / update / verify / push — resolve versioned rule profiles against the CodeCharter portal, keep codecharter.lock.json in sync, verify the local bundle cache, and upload rule and profile drafts.
• config — inspect, validate and edit .codecharter/config.yml, including the config.local.yml overlay.
• coverage — run tests with coverage collection and gate on a minimum line-coverage percentage.
• mcp / install — run the CodeCharter MCP server (Model Context Protocol) and register it with an AI coding tool, so analysis is available on demand.
• lsp / config-lsp — language servers for .ccr rules and for .codecharter/config.yml.
• auth / login / logout — manage the credentials stored on this machine.

Run codecharter --help or codecharter <command> --help for the full surface.

Runtime requirements

This tool is part of a commercial product. Installing the package does not grant a usage right. A valid CodeCharter license or API key is required at runtime; without it the CLI will not perform analysis.

See https://codecharter.tools for documentation, and https://codecharter.tools/docs/cli/license for how to obtain a license and configure it.