{
 "schema_version": 1,
 "generated": "2026-10-20",
 "id": "scarletkc-seiso--agent-repairs-seiso-findings",
 "repo": "scarletkc/seiso",
 "repo_url": "https://github.com/scarletkc/seiso",
 "repo_slug": "scarletkc-seiso",
 "title": "Have an agent repair Seiso findings in project docs",
 "page_title": "How to have an agent repair Seiso findings in project docs with Seiso",
 "summary": "Let a coding agent use Seiso diagnostics to fix most doc findings and rerun the check.",
 "who": "A developer who wants an AI agent to clean up a docs folder after a large batch of AI-written pages.",
 "problem": "Each finding must be fixed by hand, and some fixes need a judgment about which page owns a fact.",
 "outcome": "A set of doc edits where mechanical findings are fixed and judgment calls are listed with the decision each one needs.",
 "steps": [
  "Run `seiso check` at the repository root and save the findings.",
  "Run `seiso rule --all` to see each rule's status.",
  "For a rule you do not understand, explain it with `seiso rule <rule-name>`. (inferred, check the README)",
  "Edit the named files to apply each fix, leaving judgment calls for a human to decide.",
  "Run `seiso check` again and confirm the findings are gone or listed as decisions."
 ],
 "agent_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.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "45 minutes",
 "basis": "readme",
 "caveat": "The README says a fix that needs a judgment, such as which of two pages owns a fact, is named as a decision rather than made by Seiso, so an agent still needs a human to settle those.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "rust",
 "requirements": [
  "A repository with Markdown project docs",
  "One install route: cargo, uv or pipx, or npm",
  "A shell at the repository root"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.9,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/scarletkc-seiso/agent-repairs-seiso-findings/",
 "md": "https://dedupedai.com/use-cases/scarletkc-seiso/agent-repairs-seiso-findings/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/scarletkc-seiso--agent-repairs-seiso-findings.json",
 "api_version": "v1"
}