Menú
Fix bugs in the forked release-please ecosystem (vm0-ai/release-please + vm0-ai/release-please-action)
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.
Basado en la clasificación ocupacional SOC
Start the development server in background mode
Start dev server and interact with the platform via agent-browser. Use when user asks to browse, test, or demo the platform UI, connect services, or perform any browser-based interaction with the local dev environment.
Reset turbo environment (clean node_modules, reinstall, sync DB)
Check if a PR, commit, or tag has been deployed to production
Query, investigate, and manage Sentry issues for debugging and incident response
Create or update a PR and hand it off to a coding agent worker via load balancing. Removes pending label if present, then assigns a worker.
| name | fix-release-please |
| description | Fix bugs in the forked release-please ecosystem (vm0-ai/release-please + vm0-ai/release-please-action) |
| context | fork |
Fix a bug in the project's forked release-please core library, then rebuild the GitHub Action.
| Repo | Fork of | Branch | Role |
|---|---|---|---|
vm0-ai/release-please | googleapis/release-please | vm0 | Core library (TypeScript/Node) |
vm0-ai/release-please-action | googleapis/release-please-action | vm0 | GitHub Action wrapping the core library |
.github/workflows/release-please.yml uses vm0-ai/release-please-action@vm0package.json has "release-please": "github:vm0-ai/release-please#vm0"Your args are: $ARGUMENTS
Parse the args to understand what bug to fix. If no args provided, ask the user what the issue is.
cd /tmp && rm -rf release-please release-please-action
git clone https://github.com/vm0-ai/release-please.git
git clone https://github.com/vm0-ai/release-please-action.git
cd /tmp/release-please && git config user.email "noreply@vm0.ai" && git config user.name "vm0-ai"
cd /tmp/release-please-action && git config user.email "noreply@vm0.ai" && git config user.name "vm0-ai"
Create a fix branch from main, make the fix, then cherry-pick to vm0:
cd /tmp/release-please
git checkout main
git checkout -b fix/<description>
# ... make the fix, write tests to verify, commit ...
git push origin fix/<description>
git checkout vm0
git cherry-pick <commit-sha>
git push origin vm0
This step is always required after any core library change:
cd /tmp/release-please-action
git checkout vm0
npm install
npm run build
git add package-lock.json dist/index.js
git commit -m "fix: <same description as the core fix>"
git push origin vm0
cd /tmp/release-please && git log --oneline vm0 -5
cd /tmp/release-please-action && git log --oneline vm0 -5
Report what was changed.
If the user asks to sync with upstream:
cd /tmp/release-please
git remote add upstream https://github.com/googleapis/release-please.git
git fetch upstream
git checkout vm0
git rebase upstream/main
# Resolve conflicts if any
git push origin vm0 --force-with-lease
Then rebuild the action (Step 3).