Check Chatto release readiness, including release metadata, upgrade guidance, and docs website consistency. Use when preparing or reviewing a Chatto release or release PR.
87%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Read the release process. Paths below are relative to the repository root. This checklist applies to Chatto, not the independently versioned products and libraries in this repository.
During release preparation or PR review, check the proposed release commit and available CI evidence. Mark publication checks as pending until publication occurs; missing published artifacts at this stage are not failures.
MINIMUM_SUPPORTED_SERVER_VERSION and
MINIMUM_CONNECTABLE_SERVER_VERSION against root AGENTS.md. Verify the
required PR labels and explanations, including the justification and
operator upgrade action for a connection-threshold increase.When preparing or reviewing a Chatto release, check the docs website as well
as the release page. Read docs/RELEASING.md#documentation-channels to
distinguish stable documentation from development documentation.
Release Notes action in
apps/docs-website/src/content/docs/index.mdx. It must link to the release
page for the latest stable minor version represented by the site. Preparing
an unreleased page alone does not make it the latest stable release.apps/docs-website/astro.config.mjs and links
from guides to release notes. Verify that target pages and fragments exist
and match the release discussed. Preserve intentional historical links.apps/docs-website/AGENTS.md.
Report required corrections to protected pages unless the user has requested
those edits. For review-only tasks, report findings without edits.Use the release process for the expected artifacts and publication workflows. Check each applicable target separately:
@chatto/client npm package.Confirm that artifacts and workflow results match the intended version and source commit. Check GitHub's draft and prerelease status; only the highest stable Chatto version must claim Latest. A successful server workflow or GitHub release does not prove that every publication target succeeded.
Report each target as verified, pending, failed, or not applicable, with evidence or the reason. Follow the release process for partial publication and retries; do not rebuild a published version with changed contents.
Run mise x -- pnpm --filter docs-website build after page edits. Report
findings, checks run, and checks still needed. Do not claim release readiness
from documentation checks alone. This checklist does not authorize tagging,
publication, deployment, or approval of release workflows.
chattocorp/chatto
da08d92
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.