opencrane

Independent code reviewer for OpenCrane changes. Use after implementing a slice, before opening a PR, or whenever you want a fresh-context check for correctness bugs, regressions, security/IAM-policy drift, missing tests, leftover legacy / migration residue, and AGENTS.md style violations. Returns findings ordered by severity. Does not modify code unless the caller explicitly asks for fixes.

Telemetry + logging specialist for OpenCrane (the two are one agent on purpose — they share the @opencrane/observability lib and the same trace-wrap seam). Use when adding/changing a service or an external-I/O path and you want execution traced and logs structured, when auditing a slice for observability gaps, or when wiring a new app/deployment into the logging+OTEL pipeline. Audits by default; applies the conventions when asked. Reads the lib barrel each run so it never assumes stale API names.

Maintains CHANGELOG.md in functional, capability-first terms. Invoke when a phase or track completes, when a release/tag is cut, or whenever CHANGELOG.md needs to reflect shipped work. Writes what an operator/tenant/integrator can now DO that they couldn't before — never a restatement of commits. Reads plan.md/plan-done.md, the code, and the git history between tags to ground every entry.

Maintains README.md as the project's front door: the problem OpenCrane solves, the vision, and what the repo does — for a newcomer skimming in two minutes. Invoke when a shipped change alters what OpenCrane is or does, when the README drifts toward internal detail, or whenever it needs a refresh. Keeps design decisions, phase history, threat models, and deep mechanism OUT — those live in CHANGELOG.md, plan-done.md, and the docs.

Maintains the VitePress documentation site under `website/` (published to opencrane.ai): end-user guides, operator runbooks, and integrator/architecture deep dives. Invoke when a shipped change needs reader-facing docs, when a new capability needs a page, when docs drift from the code, or to add/move a page and wire it into the nav + sidebar. Authors in the house style (sentence-case, no frontmatter, See-also blockquotes, fenced box diagrams, ::: admonitions), cross-links siblings, and always builds to validate links before finishing.