Starr-del
UserOffline deploy-safety skills for Claude Code. Zero credentials, zero network, zero dependencies.
Categories
Indexed Skills (20)
bundle-weight
Audit package.json for heavyweight dependencies, duplicate-purpose libraries, and misplaced build tools before they bloat bundles and slow cold starts. Use when the user mentions slow builds, large bundles, slow page loads, serverless cold starts, 'why is my app heavy', dependency cleanup, or when reviewing any package.json. Runs fully offline — no API keys, no network, no credentials.
ci-workflow-doctor
Lint GitHub Actions workflows for deploy-breaking and security mistakes. Use whenever the user writes or edits a workflow file, mentions GitHub Actions, sets up CI/CD, complains that deploys land out of order, or before the first automated deploy of a project. Also run it during any security review of a repo. Runs fully offline — no API keys, no network, no credentials.
cors-auditor
Audit CORS configuration in Express, Next.js, FastAPI, or Flask code for security misconfigurations. Use whenever the user mentions CORS errors, 'blocked by CORS policy', cross-origin issues, configures an API for a frontend, or asks why credentials/cookies aren't being sent cross-origin. Also run it before deploying any API. Runs fully offline — no API keys, no network, no credentials.
deploy-log-doctor
Diagnose failed build and deploy logs from Vercel, Netlify, Cloudflare Pages, or GitHub Actions. Use this whenever the user pastes a build log, says a deploy failed, mentions 'build error', 'deployment failed', 'works locally but not in production', or shows any CI output containing an error — even if they don't ask for a diagnosis explicitly. Runs fully offline — no API keys, no network, no credentials.
dns-cutover
Generate the exact DNS records for pointing a custom domain at Vercel, Netlify, Cloudflare Pages, or GitHub Pages — and validate the user's actual records before they flip the domain. Use whenever the user mentions custom domains, DNS, nameservers, 'domain not working', CNAME/A records, or connecting a purchased domain to a deployed site. Runs fully offline — no API keys, no network, no credentials.
env-drift
Find environment-variable drift between code, .env files, .env.example, and platform config (vercel.json / netlify.toml). Use whenever a deploy fails with undefined env vars, the user mentions 'missing environment variable', 'works locally but env is undefined in prod', sets up a new deploy environment, onboards a teammate, or before any first deploy of a project. Runs fully offline — no API keys, no network, no credentials.
lockfile-doctor
Diagnose package-manager and lockfile drift that causes 'works on my machine' deploy failures. Use whenever an install behaves differently in CI than locally, the user mentions lockfile conflicts, npm/pnpm/yarn confusion, 'npm ci failed', non-reproducible builds, or when auditing any Node project before deploy. Runs fully offline — no API keys, no network, no credentials.
migration-reversibility
Check SQL migration files for irreversible or deploy-breaking operations before running them against production. Use whenever the user writes a migration, mentions ALTER/DROP/migrate, prepares a release containing schema changes, or asks if a deploy is safe — for Supabase, Prisma, Drizzle, or raw SQL alike. Runs fully offline — no API keys, no network, no credentials.
rollback-readiness
Score how safely a project can be deployed AND rolled back — the final pre-push check. Use whenever the user says they're about to deploy, ship, launch, or push to production, asks 'is this ready to deploy', finishes a feature destined for prod, or at the end of any session that produced deployable changes. Run this proactively; it is the capstone check of the preflight pack. Runs fully offline — no API keys, no network, no credentials.
secret-preflight
Scan a repository for committed secrets, API keys, tokens, and private keys before deploying or pushing. Use before any first push to a public repo, before any deploy, when the user mentions 'did I commit a secret', 'API key in code', security review, or open-sourcing a project — and proactively if you notice a hardcoded credential while doing other work. Runs fully offline — no API keys, no network, no credentials.
bundle-weight
Audit package.json for heavyweight dependencies, duplicate-purpose libraries, and misplaced build tools before they bloat bundles and slow cold starts. Use when the user mentions slow builds, large bundles, slow page loads, serverless cold starts, 'why is my app heavy', dependency cleanup, or when reviewing any package.json. Runs fully offline — no API keys, no network, no credentials.
ci-workflow-doctor
Lint GitHub Actions workflows for deploy-breaking and security mistakes. Use whenever the user writes or edits a workflow file, mentions GitHub Actions, sets up CI/CD, complains that deploys land out of order, or before the first automated deploy of a project. Also run it during any security review of a repo. Runs fully offline — no API keys, no network, no credentials.
cors-auditor
Audit CORS configuration in Express, Next.js, FastAPI, or Flask code for security misconfigurations. Use whenever the user mentions CORS errors, 'blocked by CORS policy', cross-origin issues, configures an API for a frontend, or asks why credentials/cookies aren't being sent cross-origin. Also run it before deploying any API. Runs fully offline — no API keys, no network, no credentials.
deploy-log-doctor
Diagnose failed build and deploy logs from Vercel, Netlify, Cloudflare Pages, or GitHub Actions. Use this whenever the user pastes a build log, says a deploy failed, mentions 'build error', 'deployment failed', 'works locally but not in production', or shows any CI output containing an error — even if they don't ask for a diagnosis explicitly. Runs fully offline — no API keys, no network, no credentials.
dns-cutover
Generate the exact DNS records for pointing a custom domain at Vercel, Netlify, Cloudflare Pages, or GitHub Pages — and validate the user's actual records before they flip the domain. Use whenever the user mentions custom domains, DNS, nameservers, 'domain not working', CNAME/A records, or connecting a purchased domain to a deployed site. Runs fully offline — no API keys, no network, no credentials.
env-drift
Find environment-variable drift between code, .env files, .env.example, and platform config (vercel.json / netlify.toml). Use whenever a deploy fails with undefined env vars, the user mentions 'missing environment variable', 'works locally but env is undefined in prod', sets up a new deploy environment, onboards a teammate, or before any first deploy of a project. Runs fully offline — no API keys, no network, no credentials.
lockfile-doctor
Diagnose package-manager and lockfile drift that causes 'works on my machine' deploy failures. Use whenever an install behaves differently in CI than locally, the user mentions lockfile conflicts, npm/pnpm/yarn confusion, 'npm ci failed', non-reproducible builds, or when auditing any Node project before deploy. Runs fully offline — no API keys, no network, no credentials.
migration-reversibility
Check SQL migration files for irreversible or deploy-breaking operations before running them against production. Use whenever the user writes a migration, mentions ALTER/DROP/migrate, prepares a release containing schema changes, or asks if a deploy is safe — for Supabase, Prisma, Drizzle, or raw SQL alike. Runs fully offline — no API keys, no network, no credentials.
rollback-readiness
Score how safely a project can be deployed AND rolled back — the final pre-push check. Use whenever the user says they're about to deploy, ship, launch, or push to production, asks 'is this ready to deploy', finishes a feature destined for prod, or at the end of any session that produced deployable changes. Run this proactively; it is the capstone check of the preflight pack. Runs fully offline — no API keys, no network, no credentials.
secret-preflight
Scan a repository for committed secrets, API keys, tokens, and private keys before deploying or pushing. Use before any first push to a public repo, before any deploy, when the user mentions 'did I commit a secret', 'API key in code', security review, or open-sourcing a project — and proactively if you notice a hardcoded credential while doing other work. Runs fully offline — no API keys, no network, no credentials.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.