Show HN: Dari-docs – Optimize your docs using parallel coding agents
Dari-docs is a command-line interface designed to enhance the clarity of documentation for developer agents. It tests documentation by simulating developer tasks and identifies areas where agents encounter difficulties. The tool provides feedback and proposed edits to improve documentation quality, ensuring it is agent-readable.
- ▪Dari-docs tests documentation by sending it to simulated developer agents who attempt to complete tasks using only the provided docs.
- ▪It identifies task-blocking ambiguities, such as unclear setup instructions and inconsistent terminology.
- ▪The tool can generate proposed documentation edits based on the feedback from the simulated agents.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/mupt-ai/dari-docs |
| Publication time | Wed, 20 May 2026 16:53:07 +0000 |
| Retrieval time | 2026-05-20T17:05:02.733Z |
| Last seen | 2026-05-20T17:05:02.733Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | R9bD3cuZ_beo |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
dari-docs Make your docs so good even the dumbest agent can ship. dari-docs is a CLI for testing whether your documentation is clear enough for agents to use. It sends your docs to simulated developer agents, asks them to complete real tasks, reports where they get stuck, and can generate proposed docs edits from that feedback. Use it to turn documentation quality from “seems understandable” into “an agent can actually complete the task.” Why dari-docs? Good docs used to mean “a developer can eventually figure this out.” That is no longer enough. When the reader is an agent, ambiguity becomes measurable.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.