release-checklist

To generate a release validation checklist, the skill reads project context from CLAUDE.md and current milestones, scans the codebase for issues, and assembles a platform-aware release document. You can invoke it and specify your target platform to tailor the output.

Finding outstanding TODO, FIXME, and HACK notes before a release is automated by scanning the codebase for these markers. The skill aggregates them with their file locations and severity into a structured readiness document.

A pre-release checklist for production milestones includes sections for code health, build readiness, quality gates, content completeness, platform readiness, and launch go/no-go criteria, tailored by reading milestone configurations.

Yes, the release checklist works without CI-CD build verification logs. It checks for test results in CI logs or test outputs when available, but primarily relies on scanning codebase issues and reading milestone context.

Yes, you need a CLAUDE.md file to use the automated release checklist. The skill reads this file to gather project context, version information, and platform targets required to generate the validation document.

You can automate build verification and quality gate checks by generating a comprehensive validation document. The skill aggregates platform-specific readiness sections and checks test outputs to satisfy deployment requirements.