Menú
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/ai-dynamo/aitune --skill aitune-releaseEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Use when a user asks to tune, optimize, accelerate, or deploy a PyTorch model or inference pipeline for GPU performance.
Use when measuring inference performance of a PyTorch model before and after AITune optimization — capturing baseline, compilation time, tuned throughput, and speedup.
Use when creating a git commit to ensure the message follows the Conventional Commits specification
Basado en la clasificación ocupacional SOC
Mostrando SKILL.md
| name | aitune-release |
| description | Use when creating a new release tag for the project |
| allowed-tools | Bash |
| license | Apache-2.0 |
Before tagging, verify:
Working tree is clean:
git status --short
If there are uncommitted changes, stop and ask the user to commit or stash them first.
Current branch is main and up to date:
git branch --show-current
git fetch origin && git status
Latest pipeline on main is passing — check in CI/CD pipelines before tagging. A tag pushed against a failing pipeline will trigger a broken deploy. Stop and ask the user to confirm the pipeline is green.
Read the latest tag from origin:
git fetch --tags origin
git tag --sort=-version:refname | head -5
Ask the user: major, minor, or patch?
Compute the next version:
v1.2.3v2.0.0, Minor → v1.3.0, Patch → v1.2.4Propose the tag (e.g. v1.3.0) and wait for confirmation.
On confirmation, create an annotated tag and push:
git tag -a v1.3.0 -m "Release v1.3.0"
git push origin v1.3.0
Pushing the tag triggers the GitLab CI tag pipeline automatically.