ci-release-wasp-drone — Claude Code subagent: CI and release work
ci-release-wasp-drone — a subagent for GitHub Actions and npm release plumbing on a SvelteKit app hosted on Vercel. Handy when a pipeline builds twice or a release step is unclear.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install platform-and-release-tools@wasp-nestWhat ci-release-wasp-drone does
This subagent handles CI and release work for a SvelteKit app running on Vercel. It designs GitHub Actions jobs around pnpm, type checking, lint, unit and e2e tests, then the build. It also maps how Vercel's own build and preview deploys overlap with Actions, so a single commit doesn't get compiled twice.
Other ground it covers: gating Drizzle migrations against Neon inside the pipeline, delivering secrets with Doppler and OIDC, cache choices, required status checks, and picking release automation (changesets, semantic-release, or none). A second, older case is npm publishing for @deeplake/hivemind — esbuild bundling, version syncing, a tsc + vitest + jscpd gate, a files allowlist, prepack, and a secret scan before the package ships.
It works from its own knowledge base in the ci-release-stinger skill and searches further when that runs dry. Scope is narrow by design: Vercel platform settings, Drizzle migration mechanics, the Doppler model and CVE audits belong to sibling subagents, so asking this one for them burns a turn.
What it helps with
- design Actions jobs for pnpm, lint and e2e runs
- kill a duplicate build between Vercel and Actions
- gate Drizzle migrations to Neon in the pipeline
- pull Doppler secrets into Actions over OIDC
- publish an npm package without leaking a secret
Example prompts for the agent
- Design our CI: pnpm, typecheck, lint, unit and e2e jobs, and make sure Vercel doesn't build the same commit twice.
- Why did Vercel build twice? Audit our workflows and tell me what to fix.
- Gate the Drizzle migration to Neon in CI and wire Doppler in through OIDC.
How to install ci-release-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install platform-and-release-tools@wasp-nest2Manually: put the files in place
.claude/agents/ci-release-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/ci-release-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/ci-release-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about ci-release-wasp-drone
How do I install ci-release-wasp-drone in Claude Code?
From the marketplace: /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install platform-and-release-tools@wasp-nest. The agent file sits at .claude/agents/ci-release-wasp-drone.md.
What does ci-release-wasp-drone do?
It covers CI and releases for a SvelteKit app on Vercel: GitHub Actions job design, the overlap between Vercel builds and Actions, migration gating, secret delivery, and the call on release automation.
Which jobs should go to a different subagent?
Vercel platform configuration, Drizzle migration mechanics, the Doppler model and CVE audits are other agents' territory. This one flags the concern and hands it off.