Menu
Use this if you want to update all project dependencies while respecting semver compatibility.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when designing, implementing, reviewing, debugging, or documenting Chatto event-sourced domain behavior, including EVT subjects, aggregate boundaries, Services, projections, optimistic concurrency control, read-your-writes, live/reconnect delivery, replay compatibility, migration safety, and rollback/deployment implications.
Create or update Chatto docs website release pages by comparing release-please state, tags, commits, changelog entries, and PRs
Run a full review of all Architecture Decision Records for implementation drift, contradictions, stale decisions, missing supersession notes, weak rationale, and missing cross-references. Use when the user asks for an ADR review, ADR audit, stale ADR check, architecture decision consistency check, or wants to verify ADRs against the current codebase, feature/design records, architecture docs, glossary, or public API state.
Update docs/ARCHITECTURE.md to reflect the current state of the codebase by examining code and documentation.
Run a documentation-focused maintenance checkup of the Chatto codebase. Fans out to /fdr, /adr, and /chatto-architecture, then compiles a single consolidated report. Always propose-only — no changes applied without explicit user approval. At the end, points the human at other maintenance skills (/update-project-dependencies, /chatto-security-review) they may want to run themselves.
Production debugging tools for NATS streams, KV buckets, and protobuf events. Covers nats CLI commands, stream inspection, protobuf decoding, and message iteration.
| name | update-project-dependencies |
| description | Use this if you want to update all project dependencies while respecting semver compatibility. |
This skill updates all project dependencies while respecting semver compatibility, then runs tests to verify everything still works.
Follow these steps in order:
Before making any changes, read and save the current dependency versions:
cli/go.mod - note the versions of direct dependencies (the require blocks without // indirect)frontend/package.json - note the versions in devDependenciesRun these commands in the cli/ directory:
cd cli && go get -u ./...
cd cli && go mod tidy
Note: go get -u updates to the latest minor/patch versions respecting the module's compatibility guarantees.
Run this command in the frontend/ directory:
cd frontend && pnpm update
This updates packages within their semver ranges defined in package.json.
Execute the full test suite:
mise run test
If tests fail: Stop here and report the failures. Do NOT attempt to rollback the changes - leave them in place so the user can review and fix manually.
After completing the updates, provide a summary report with this structure:
| Package | Previous | Updated |
|---|---|---|
| package-name | v1.2.3 | v1.2.5 |
| Package | Previous | Updated |
|---|---|---|
| package-name | ^1.2.3 | ^1.2.5 |
Highlight any significant updates, especially: