claylo/bito
Quality gate tooling for building-in-the-open artifacts
Platform-specific configuration:
{
"mcpServers": {
"bito": {
"command": "npx",
"args": [
"-y",
"bito"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
[](https://github.com/claylo/bito/actions/workflows/ci.yml) [](https://crates.io/crates/bito) [](https://docs.rs/bito) [](https://github.com/claylo/bito)
bito = building in the open.
bito is part of the building-in-the-open approach to AI-assisted development — a set of practices, templates, and tools for teams that work with coding agents. It can be used entirely on its own; the broader framework just gives it more context to work with.
AI coding agents generate documentation as they work — ADRs, design docs, changelogs, handoff notes. The quality varies between sessions. Sometimes you get crisp, well-structured prose. Sometimes you get bloated walls of text that no one wants to review.
bito catches the problems before you commit. It runs 18 deterministic writing checks — readability scoring, token budgets, section completeness, grammar, dialect enforcement, and style analysis. No LLM, no API calls, no network. Same input, same result, every time.
The goal: agent-generated documents that are clean enough to ship.
$ bito analyze docs/architecture.md
docs/architecture.md
Readability: Grade 12.4, 24 sentences, 390 words
Grammar: 8 issues, 3 passive (12.5%)
Sticky: Glue index 21.5%, 2 sticky sentences
Pacing: Fast 62% / Medium 29% / Slow 8%
Length: Avg 15.8 words, variety 10.0/10
Transitions: 0% of sentences, 0 unique
Overused: "template" (1.3%), "skill" (1.1%), "design" (1.1%)
Diction: 2 vague words
Style: Score 92/100, 2 adverbs, 0 hidden verbs`analyze` runs 18 checks in one pass:
| Category | What it catches | |----------|----------------| | Readability | Flesch-Kincaid grade l
Loading reviews...