Menu
Use when publishing snapshot (pre-release test) versions of SDK packages to npm, without affecting real versions or main branch
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | snapshot |
| description | Use when publishing snapshot (pre-release test) versions of SDK packages to npm, without affecting real versions or main branch |
Publishes @aave packages as snapshot versions to npm using changesets. Snapshot versions follow the format 0.0.0-<tag>-<timestamp> and do not affect real semver versions.
You MUST use TodoWrite to create a todo for EACH step below. Mark each complete only after verification.
preview). Ask if not specified.nvm use to ensure correct Node.js versioncorepack enable to ensure correct pnpm versionpnpm install to update dependenciespnpm changeset status to confirm pending changesets exist (if none, STOP and inform user)pnpm build to build all packagesnpm whoami
npm login then re-verifypnpm changeset version --snapshot <tag> to stamp snapshot versions0.0.0-<tag>-<timestamp> versionspnpm changeset publish --tag <tag> in their terminal
git checkout -- .
| Condition | Action |
|---|---|
| No pending changesets | Nothing to snapshot - inform user |
npm whoami fails | User must run npm login |
| Build fails | Fix build before publishing |
| Publish requires interactive auth | Hand the pnpm changeset publish command to the user to run in their own terminal |
changeset version --snapshot modifies package.json files; always restore with git checkout -- . after publishchangeset publish requires interactive browser passkey auth; always hand this command to the user to run in their terminalversion and publish must match, otherwise consumers can't install by tag