agentsclimarketplace
Sign in

Architecture audit

Skill khmilevoi/rpi-deploy/.claude/skills/architecture-audit

Use when asked to check, sync, or audit docs/architecture/ against the code — verifies every diagram and walkthrough against its Source anchors and fixes drift.From its SKILL.md

Install
npx -y skills add khmilevoi/rpi-deploy --skill architecture-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, as published. Nobody here has run it

Architecture Audit

Full sweep of docs/architecture/ against the code. The outcome is fixed docs, not a report of suggestions. Conventions and the code-area→doc map live in the architecture-diagrams skill — read it first.

Procedure

  1. Inventory. List every .md under docs/architecture/ (including flows/). README.md is checked for link integrity and listing completeness only (it deliberately has no anchors).
  2. Per document:
    • Read its Source anchors. Anchor pointing at a missing file → drift.
    • Read every anchored file. Compare against the diagram AND the prose walkthrough: stage names/order, participants, states, failure branches.
    • Fix any mismatch by editing the doc (diagram, walkthrough, and anchors together — all three must stay consistent). Follow the template and Mermaid style rules from architecture-diagrams.
  3. Orphan check, both directions:
    • Docs → code: anchors referencing deleted/renamed files.
    • Code → docs: rows of the code-area→doc map in architecture-diagrams whose code area has files not reflected in the mapped doc; plus new modules under crates/*/src/ and new cli//agent/ files matching no map row at all. A genuinely new area may need a new flows/<name>.md — create it from the template, and add a map row to architecture-diagrams in the same change.
  4. Report. One list: doc — what drifted — what was changed. If nothing drifted, say "zero drift" explicitly.
  5. Commit doc fixes as docs(architecture): sync <doc> with code (one commit for the sweep is fine).

What counts as drift

  • Diagram or walkthrough contradicts current code behavior.
  • Anchor list stale (missing files that shaped the doc; listing dead paths).
  • Walkthrough failure branches that no longer exist (or new prominent ones missing).
  • README index missing a doc or linking a dead file.

Cosmetic differences (wording, layout) are not drift — do not churn docs.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.