create-release-checklist
Create Release Checklist
Overview
Generate a structured, actionable release checklist that covers the full deployment lifecycle from code freeze to post-deploy verification. The output is a markdown file with checkboxes and owner assignments saved to .chalk/docs/engineering/.
Workflow
-
Read project context — Check for
.chalk/docs/engineering/files to understand:- Architecture and deployment topology (monolith vs. microservices, deploy targets)
- Existing monitoring and alerting setup
- Database migration patterns
- Feature flag infrastructure
- Previous release checklists (to inherit any project-specific items)
- CI/CD pipeline configuration
-
Determine the version — From
$ARGUMENTS:- If a version is provided, use it
- If not, check
package.json,pyproject.toml,Cargo.toml, or equivalent for the current version and suggest the next one based on the changes (semver)
More from generaljerel/chalk-skills
python-clean-architecture
Clean architecture patterns for Python services — service layer, repository pattern, domain models, dependency injection, error hierarchy, and testing strategy
23create-handoff
Generate a handoff document after implementation work is complete — summarizes changes, risks, and review focus areas for the review pipeline. Use when done coding and ready to hand off for review.
16create-review
Bootstrap a local AI review pipeline and generate a paste-ready review prompt for any reviewer agent. Use after creating a handoff or when ready to get an AI code review.
15fix-findings
Fix findings from the active review session — reads reviewer findings files, applies fixes by priority, and updates the resolution log. Use after pasting reviewer output into findings files.
15fix-review
When the user asks to fix, address, or work on PR review comments — fetch review comments from a GitHub pull request and apply fixes to the local codebase. Requires gh CLI.
15review-changes
End-to-end review pipeline — creates a handoff, generates a review (self-review or paste-ready for another provider), then offers to fix findings. Use when you want to review your changes before pushing.
13