| name | release-readiness |
|---|---|
| description | Use when preparing mq-image-analyze for release by checking version sync, docs, tests, CLI, MCP tools, model safety, examples, and Git state. |
Use this skill before tagging or publishing mq-image-analyze.
- "is mq-image-analyze ready to release?"
- "run the release checklist"
- "check version and changelog alignment"
- "what's blocking the release?"
- "update the docs" → use
docs-maintainer - "add a CLI flag" → use
cli-maintainer - "change a model backend" → use
model-setup-maintainer
git status --shortVERSIONpyproject.tomlCHANGELOG.mdREADME.mdSKILLS.mddocs/release.mddocs/json-schema.mddocs/mcp-tools.mddocs/tool-safety.mdscripts/validate.shrelease-check.sh
- dirty worktree with unrelated changes
- version mismatch between
VERSION,pyproject.toml, README, and changelog - failing tests
- CLI entry point failure
- tracked model weights or
.env - docs missing new CLI/MCP/JSON behavior
- skill status drift
- output contract changes without schema/tests
bash scripts/validate.sh
bash release-check.shIf a narrower check is enough:
python -m compileall mq_image_analyze -q
python -m pytest -q
mq-image --help
mq-image --versionReturn:
- status: ready, blocked, or uncertain
- blockers
- changed files
- checks run
- checks skipped and why
- model/API credentials not verified, if applicable