CLI Reference
Overview
Top-level Fensu commands, help, version output, and exit-code conventions.
The fensu command initializes policy, checks repositories, reports duplicated
code, explains rules, maps call flow, installs generated agent guidance, and
manages analyzer targets.
fensu --helpUsage: fensu {init,check,dupes,rule,map,skills,target} ...
Commands: init Initialize Fensu configuration for a repository. check Evaluate repository architecture rules. dupes Report duplicated code (advisory; never fails on findings). rule Show details for one rule. map Render a directional project call map. skills Generate and install agent guidance. target Add an explicit analyzer target.Commands
Section titled “Commands”| Command | Purpose |
|---|---|
fensu init | Detect a repository and write starting configuration. |
fensu check | Evaluate blocking rules and optional warnings. |
fensu dupes | Report duplicated code as advisory review input. |
fensu rule | Inspect one configured rule. |
fensu map | Render a downstream or upstream project call tree. |
fensu skills | Generate, install, and verify project agent guidance. |
fensu target | Add a validated SvelteKit analyzer target. |
Run fensu <command> --help for command-specific options.
Version
Section titled “Version”Both help forms exit 0:
fensu --helpfensu -hPrint the installed package version with:
fensu --versionfensu 0.4.0Exit codes
Section titled “Exit codes”Commands generally use 0 for success and 2 for usage, configuration, or setup
errors. fensu check uses 1 for blocking faults, fensu dupes exits 0
whatever it finds, and
fensu skills --check uses 1 when generated files need an update. See
each command page for its complete contract.