release-checklist

You can automate release readiness by reading project context and version information from CLAUDE.md, scanning milestones for required content, and checking build health. This generates a Markdown checklist stored under production/releases for audit purposes.

Release readiness validation ensures your project is prepared for deployment by covering build health, compliance requirements, storefront metadata, and publishing checks. It aggregates unresolved code notes and milestone requirements into a single comprehensive overview.

Yes, the Skill reads CLAUDE.md to gather project context, version information, and platform targets. This context-aware planning ensures the generated checklist aligns checks specifically to your current release scope across platforms.

You can track unresolved code annotations by scanning the repository for TODO, FIXME, and HACK notes as part of automated release health checks. These are consolidated into a Markdown checklist for review.

No, this release management automation has zero dependencies. It directly reads your CLAUDE.md file and production milestones to generate the checklist without requiring external modules or components.

Release checklists should be stored under the production/releases directory. The Skill automatically generates a detailed Markdown document in this location to ensure long-term traceability and audit readiness for your deployment process.