Objective
A local coding assistant ecology keeps private source code on controlled hardware while using specialists for review, test generation, migration planning, and documentation.
Specialists
| Specialist | Job |
|---|---|
| diff explainer | Summarizes patch intent and risk. |
| test generator | Proposes unit and integration tests. |
| migration planner | Finds old APIs and suggests phased changes. |
| style checker | Applies project conventions. |
| security reviewer | Flags risky dependencies, secrets, and trust boundary changes. |
Request flow
PROCEDURE review_patch_locally(diff, repo_context)
contracts <- LOAD_PROJECT_CONTRACTS(repo_context)
explanation <- RUN_SPECIALIST("diff-explainer", diff, contracts)
tests <- RUN_SPECIALIST("test-generator", diff, contracts)
risks <- RUN_SPECIALIST("security-reviewer", diff, contracts)
style <- RUN_SPECIALIST("style-checker", diff, contracts)
RETURN REVIEW_BUNDLE(explanation, tests, risks, style)
END PROCEDUREBreeding loop
Use repository-local eval cases: accepted historical patches, rejected historical patches, known style examples, migration samples, and security fixtures. The best descendant is the one that improves developer speed without increasing review misses.
Source reports used for this guide
These reports are preserved verbatim in the site archive. The guide above is an editorial synthesis and may narrow, qualify, or reorganize claims from the source material.