Generate and install agent skill files from your active ruleset so agent instructions stay in sync with what CI enforces.
strata skills installs a guidance file generated from your project’s active
rules, ready for an AI agent to follow. Because it is generated from the same rule
metadata strata check enforces, the guidance your agents read cannot drift from
the rules your CI runs. There is no hand-maintained rules document to fall out of
date; you regenerate it.
update is a subcommand, not a flag. Running strata skills on its own prints
usage and exits non-zero; the command to generate files is strata skills update.
The file lists every active rule for the repository, with its family, message, and
remediation. It reflects your select and ignore configuration, so the guidance
matches exactly what strata check will enforce.
Strata will not clobber a hand-written file. If a target path already exists and
does not carry Strata’s generated marker, the update fails rather than replacing
your content:
refusing to overwrite non-generated skill file: .claude/skills/strata/SKILL.md; rerun with --force
Files Strata previously generated are updated in place. Use --force only when you
intend to replace a file Strata did not write.
Because custom rules merge into the same catalogue as core
rules, their message and remediation appear in the generated guidance once they
are configured and selected. Your project’s own conventions become part of the
instructions your agents read, generated from the rules themselves.
Regenerate whenever your ruleset changes so the committed guidance stays in sync. A
convenient place is alongside strata check in CI, or a pre-commit hook:
