---
name: cli-surface
description: Use when changing or validating Chelis CLI behavior. Focuses on corpus-based testing for chelis fmt, surf, deep, check, eval, build, and tide, plus machine-facing output invariants.
title: cli-surface
canonical_url: https://skilld.dev/gh/chelis-lang/chelis/cli-surface
last_updated: 2026-10-07T14:45:40.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install chelis-lang/chelis/cli-surface`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/cli-surface`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/chelis-lang/chelis/cli-surface) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/cli-surface`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/cli-surface --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/cli-surface --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# CLI Surface

Use this skill for any change or validation pass involving `chelis` commands.

## Default Principle

Do not trust a CLI surface that only passed one happy-path test.
Exercise it across a corpus and check both parseability and semantic invariants.

## Required Surfaces

- `chelis fmt`
- `chelis lint`
- `chelis surf`
- `chelis deep`
- `chelis check`
- `chelis validate`
- `chelis eval`
- `chelis build`
- `chelis tide` when interactive behavior is relevant
- The **style gate** (the implicit `fmt --check` + `lint --check` step
  that runs inside `build`/`check`/`validate`/`eval --file`)

## Validation Rules

- `fmt` output must remain parseable on the supported corpus
- `deep` then `surf` output must re-enter the compiler path cleanly where that path is promised
- machine-facing output should obey contract invariants
  - perfect success must not coexist with errors
  - emitted JSON should remain stable enough for downstream tools
- executable examples should keep working after formatting
- non-executable examples must not be mistaken for CLI proof artifacts
- the style gate must fail by default on non-canonical or
  lint-violating input, must succeed with `--allow-style-violations`
  (with a stderr warning), and must be silently disabled by
  `CHELIS_STYLE_GATE_DISABLE=1` for the test corpus only — verify
  each branch when changing the gate

## Chelis-Specific Checks

- run CLI integration tests, including
  `crates/chelis-cli/tests/style_gate.rs` for the gate itself
- probe both executable and illustrative examples when the behavior touches formatting or decompilation
- compare CLI claims against actual backend/evaluator behavior when the command is a thin wrapper
- when adding a new lint rule, register it in
  `crates/chelis-lint/src/registry.rs` and confirm the gate picks it
  up by running `chelis check` on a deliberately violating fixture

## Authoritative References

- User-facing CLI doc: `docs/book/src/cli.md`
- Style guide spec: `spec/01-nomenclature.md`
- Gate implementation: `crates/chelis-cli/src/style_gate.rs`
- Gate behavior tests: `crates/chelis-cli/tests/style_gate.rs`
