Files
Claro/docs/CLI.md
T
Hermes Agent d555071406 fix: stabilize learning path, reliability and legacy Windows builds
Unify beginner syntax while preserving compatibility, repair ownership and parser guards, add verified distribution tooling and VC6 Windows 98 build inputs, and clarify documentation and release status. Preserve DOS build-input line endings and exclude generated binaries/caches.
2026-10-20 22:40:19 +00:00

78 lines
1.6 KiB
Markdown

# Claro Command Line
Claro v2026.10.20.223203 supports these main commands:
```bash
claro file.claro
claro run
claro test
claro check file.claro
claro fmt file.claro
claro repl
claro new MyProject
claro examples
claro doctor
claro validate
claro package init|add|remove|list|doctor|lock
claro ide
claro --version
claro help
```
## Run a file
```bash
claro examples/hello.claro
```
## Run a project
If the current folder has `claro.project`, `claro run` uses its `main:` setting. Otherwise it tries `main.claro`:
```bash
claro run
```
## Test the package
```bash
claro test
```
## Stable package validation
```bash
claro validate
```
This runs package health checks, built-in tests, and checker passes over the lessons and main examples.
## Package starter
```bash
claro package init
claro package add text
claro package remove text
claro package list
claro package doctor
claro package lock
```
The v2026.10.20.223203 package command is a safer local project-file helper. It creates `claro.project`, `claro.lock`, and local folders under `packages/`. Package names may appear only once in `claro.project`; `claro package doctor` reports duplicate entries so the lockfile stays unambiguous. It also requires the project manifest to have exactly one non-empty `name:` field. It is not yet an online package registry.
## IDE metadata
```bash
claro ide
```
This prints simple keyword/type metadata that future editor plugins can use.
## Type checking
```bash
claro typecheck my_script.claro
```
Checks simple typed variables such as `SET score NUMBER 10` before running the script.