Menu
Pre-release validation checklist — verify versions, CI, docs, and Docker before running mise run release
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Scaffold eval test cases for an agent in backend/evals/test_cases.py, following the TestCase dataclass pattern used by DATA_AGENT_CASES, KNOWLEDGE_AGENT_CASES, and WEB_SEARCH_CASES
Verify all project documentation reflects current codebase state after feature changes
Scaffold a new Agno agent with boilerplate, register in main.py, and add config.yaml entry
Scaffold a new Agno multi-agent team with boilerplate, register in main.py, and create docs page
Scaffold a new Agno workflow with Steps, Loops, and Conditions, register in main.py, and create docs page
Scaffold a new mise task with correct headers, flags, and conventions
| name | release-checklist |
| description | Pre-release validation checklist — verify versions, CI, docs, and Docker before running mise run release |
| disable-model-invocation | true |
Run a pre-release validation to catch issues before mise run release.
Read the current version from these files and confirm they match:
pyproject.toml — version = "X.Y.Z"frontend/package.json — "version": "X.Y.Z"Also confirm uv.lock is in sync by running:
uv lock --check
If versions disagree or uv.lock is stale, report which files are out of sync.
Verify:
main branch: git branch --show-currentgit status --porcelaingit fetch origin main && git rev-parse HEAD vs git rev-parse origin/mainReport any issues.
Check the latest CI run on main:
gh run list --workflow=validate.yml --branch=main --limit=1 --json conclusion,status,headSha,createdAt
Report the status. Warn if the latest run is not success.
Verify key files exist for Docker builds:
backend/Dockerfile existsfrontend/Dockerfile existsfrontend/public/.gitkeep exists (required by frontend Dockerfile COPY)scripts/entrypoint.sh existsSpot-check that version references in documentation are not hardcoded to a stale version. Check:
README.md — should not hardcode a specific version numberCLAUDE.md — should not hardcode a specific version numberPresent a summary:
| Check | Status | Details |
|---|---|---|
| Version consistency | pass/fail | ... |
| uv.lock sync | pass/fail | ... |
| Git branch | pass/fail | ... |
| Working tree clean | pass/fail | ... |
| Local up to date | pass/fail | ... |
| CI status | pass/fail | ... |
| Docker files exist | pass/fail | ... |
| Docs version refs | pass/warn | ... |
If all checks pass, tell the user they're ready to run mise run release.
If any checks fail, list what needs to be fixed first.