Skip to main content
fensu skills installs project-specific agent guidance generated from the same policy that fensu check enforces. Regenerate it when configuration or custom rules change, or verify it without writing in CI.

​
Usage

From anywhere under the configured project:
Fensu resolves a project identity, generates one SKILL.md, and installs the same content for each supported target:
The file records the governed project path, scopes, effective configuration, blocking and warning rules, thresholds, exceptions, custom-rule practices, testing, and common navigation commands. It is generated deterministically from the current project policy.

​
Project identity

Every generated directory is named fensu-<identity>. Fensu chooses the identity in this order:
  1. [skills].name in Fensu configuration.
  2. The nearest [project].name in pyproject.toml.
  3. The directory containing the active Fensu configuration.
Names are normalized to lowercase ASCII kebab-case. Set the name explicitly when several Fensu projects could otherwise resolve to the same identity:

​
Targets

By default Fensu installs to all supported agent targets. Pass --target (which may be repeated) to install to specific ones:

​
Installation root

Local skills install at the nearest Git root by default. If no Git root exists, they install beside the active Fensu configuration. This gives a monorepo one shared agent directory while each project keeps a distinct skill name. Use --install-root project to install beside the active configuration, --install-root git to require the Git root, or pass an explicit path. Relative paths resolve from the invocation directory. In a monorepo, each project resolves its own identity, so several projects can share one Git-root agent directory:
Fensu refuses case-only identity collisions and files owned by another project rather than replacing them.

​
Options

​
Checking freshness

Use the non-writing check in CI:
Current files exit 0. Missing, stale, divergent, or malformed generated files exit 1 and list the affected paths. Ownership collisions exit 2. fensu check also prints a non-failing stale-skill notice when it can identify an installed local skill that needs regeneration.

​
Update safety

Updates across requested targets are transactional. Fensu refuses symlinks, unsafe paths, hand-written destinations, and files owned by another project. An unmanaged destination fails rather than being replaced:
Use --force only when you intend to replace an unmanaged file. Older generated skills/fensu/SKILL.md files are migrated to the project-specific path when their generated marker proves Fensu owns them. Hand-written generic skills are left alone.

​
Exit codes

​
Custom rules are included

Because custom rules merge into the same catalogue as core rules, configured blocking and warning rules appear in the generated guidance. Your repository’s own conventions become part of the instructions agents read.

​
Keeping guidance current

Regenerate whenever your ruleset changes so committed guidance stays in sync. Verify it in CI without writing:

Custom rules

Author rules whose messages flow into generated guidance.

fensu rule

Inspect a single rule’s metadata.