What do you want to do?
3 use cases
-
Check project docs against a shared Markdown convention
Run Seiso on a repo to list stable-rule findings in its Markdown docs.
- Seiso
- Software and DevOps
- Intermediate
View prompt
In the repository at <repo path>, run `seiso check` from the repository root. Report the total number of findings and the file path and rule name of the first finding. Verify that the report only lists stable rules, since preview rules are not run by default.
-
Have an agent repair Seiso findings in project docs
Let a coding agent use Seiso diagnostics to fix most doc findings and rerun the check.
- Seiso
- Software and DevOps
- Intermediate
View prompt
In the repository at <repo path>, run `seiso check`, fix the findings the diagnostics give a direct fix for, and run `seiso check` again. Report how many findings remain and list each remaining one as a decision that needs a human. Verify that no fix changed a fact that appears on more than one page without updating the page that owns it.
-
Gate doc changes with Seiso in Claude Code hooks or CI
Run Seiso automatically when an agent or a commit changes project docs.
- Seiso
- Claude Code
- Software and DevOps
- Advanced
View prompt
In the repository at <repo path>, configure a Claude Code hook that runs `seiso check` after doc edits, following the integrations guide. Report the hook configuration you added and the result of one test run. Verify that the gate runs only stable rules.
How to use Seiso
- Check you have what it needs: A repository with Markdown project docs; One install route: cargo, uv or pipx, or npm; A shell at the repository root.
- Open scarletkc/seiso on GitHub and read the README and license.
- Install Seiso with
cargo install seiso, or runuv tool install seiso, or runnpm install -g @scarletkc/seiso. - From the repository root, run
seiso init. - Review the generated
seiso.tomlfor exclusions, kind mappings, and documentation site entries before relying on results. - Run
seiso check.
These steps come from our top use case, Check project docs against a shared Markdown convention, which also has a copy-paste agent prompt.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeAbout this repo
- Who it is forMaintainers of repositories with AI-written Markdown docs, and coding agents that read or edit those docs.
- Why it is hot
- LanguageRust
- Sourcegithub.com/scarletkc/seiso · Back to Hot repos
Requirements
- A repository with Markdown project docs
- One install route: cargo, uv or pipx, or npm
- A shell at the repository root
Maintain Seiso? Add the Featured on Deduped badge
Paste this into your README:
[](https://dedupedai.com/use-cases/scarletkc-seiso/?ref=badge)
Questions about Seiso
What is Seiso?
seiso is a Rust command-line linter that checks Markdown project docs against a shared convention so that humans and AI agents can rely on them. It is an open-source project on GitHub: https://github.com/scarletkc/seiso.
Who is Seiso for?
Maintainers of repositories with AI-written Markdown docs, and coding agents that read or edit those docs.
What can I do with Seiso?
3 use cases so far, for example: Check project docs against a shared Markdown convention; Have an agent repair Seiso findings in project docs; Gate doc changes with Seiso in Claude Code hooks or CI. Each has steps and a copy-paste agent prompt.
What do I need to run Seiso?
A repository with Markdown project docs; One install route: cargo, uv or pipx, or npm; A shell at the repository root.
What are alternatives to Seiso?
Other hot AI repos in Software and DevOps: Harness2, iFixAi, Orca, Diagram Design, AI Memory.
Is Seiso safe to run?
Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.