fleet-standard-adoption
Use when bringing this repo into compliance with a GeneFoundry fleet standard (tool-naming, response-envelope, container-hardening, versioning, MCP transport, or logging) or closing its tracking issue
SKILL.md.claude/skills/fleet-standard-adoption/SKILL.md
GitHubFleet-Standard Adoption
Follow AGENTS.md first. The canonical standards live under ../genefoundry-router/docs/ (the sibling router repo for *-link; docs/ in the router):
TOOL-NAMING-STANDARD-v1.md—verb_nounsnake_case, stable, collision-free names (lets the router drop anytransform).RESPONSE-ENVELOPE-STANDARD-v1.1.md(current; supersedes v1) —success, the payload, flat execution-error fields (error_code/message/retryable/recovery_action), and_meta(data_version). v1.1 adds untrusted-content fencing and error-message sanitation (fixed/enum error fields — never reflect caller-supplied or upstream text into caller-visible fields or logs; see the FastMCP not-found reflection guard). The nestederror:{...}shape is deferred — don't use it.CONTAINER-HARDENING-STANDARD-v1.md— non-root, read-only, cap-drop, digest-pin, Trivy + SBOM.VERSIONING-STANDARD-v1.md— single-source metadata version; noserverInfo.versionframework leak.MCP-TRANSPORT-STANDARD-v1.md— single stateless/mcp(no 307 split), canonicalserverInfo/ health.- Logging & CLI Standard v1 — structured logging + CLI conventions (canonical text tracked per-repo; no router doc).
Workflow
- Read the standard's Definition of Done; check this repo against it.
- Apply the smallest change that meets the DoD; reuse the router's reference implementation rather than reinventing.
- Add or update the guard test the standard specifies so the change can't regress.
- Run
make ci-local; note residual risk. - Close the standard's tracking issue with a one-line CHANGELOG note.
Common mistakes
- Adding router-side workarounds instead of fixing the backend to the standard.
- Meeting the letter without the guard test — it regresses on the next change.