Menu
Use when preparing a versioned release of gtex-link. Walks through changelog, version bump, tag, and watching the release workflow.
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
Use when CI fails on a PR or main. Walks through reproducing locally and root-causing without bypassing checks.
Use when adding or modifying a FastAPI route in gtex-link. Walks through request/response models, route handler, service wiring, and tests.
Use when wiring a new upstream GTEx Portal endpoint into gtex-link. Walks through the spec, models, service, route, tests, and MCP exposure decision.
Use when adding, renaming, or removing an MCP tool in gtex-link. Walks through facade registration, profiles, descriptions, tests.
| name | release-readiness |
| description | Use when preparing a versioned release of gtex-link. Walks through changelog, version bump, tag, and watching the release workflow. |
main is green: latest CI run succeeded.dependabot PRs that should land first.CHANGELOG.md has an Unreleased section with all user-visible changes since the last tag.pyproject.toml and bump version. Follow semver:
MAJOR.MINOR.PATCH[Unreleased] heading in CHANGELOG.md to [X.Y.Z] - YYYY-MM-DD and add a fresh empty [Unreleased] section above it.chore(release): bump to X.Y.Z.git tag vX.Y.Z
git push origin main vX.Y.Z
The release.yml workflow runs on v* tag pushes. It runs make ci-local, validates compose configs, and builds the release Docker image.
If release.yml fails, fix on main, bump to vX.Y.(Z+1), retag.