> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fensu.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Top-level Fensu commands, help, version output, and exit-code conventions.

The `fensu` command initializes policy, checks repositories, explains rules,
maps call flow, and installs generated agent guidance.

```bash theme={null}
fensu --help
```

```text theme={null}
Usage: fensu {init,check,rule,map,skills} ...

Commands:
  init    Initialize Fensu configuration for a repository.
  check   Evaluate repository architecture rules.
  rule    Show details for one rule.
  map     Render a downstream project call map.
  skills  Generate and install agent guidance.
```

## Commands

| Command                       | Purpose                                               |
| ----------------------------- | ----------------------------------------------------- |
| [`fensu init`](/cli/init)     | Detect a repository and write starting configuration. |
| [`fensu check`](/cli/check)   | Evaluate blocking rules and optional warnings.        |
| [`fensu rule`](/cli/rule)     | Inspect one core or custom rule.                      |
| [`fensu map`](/cli/map)       | Render a downstream project call tree.                |
| [`fensu skills`](/cli/skills) | Generate, install, and verify project agent guidance. |

Run `fensu <command> --help` for command-specific options.

## Version

Both help forms exit `0`:

```bash theme={null}
fensu --help
fensu -h
```

Print the installed package version with:

```bash theme={null}
fensu --version
```

```text theme={null}
fensu 0.4.0
```

## Exit codes

Commands generally use `0` for success and `2` for usage, configuration, or setup
errors. `fensu check` uses `1` for blocking faults, and
`fensu skills --check` uses `1` when generated files need an update. See
each command page for its complete contract.