Blackman99

Airing — DevOps skill for Claude Code

DevOps community

See which .env, .git, keys and source maps Cloudflare Pages, Vercel, Netlify or Firebase would publish — before your agent deploys, and after it's live.

How to install Airing

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Blackman99/airing and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Airing does

See which .env, .git, keys and source maps Cloudflare Pages, Vercel, Netlify or Firebase would publish — before your agent deploys, and after it's live. CLI + live probe + Claude Code hook + MCP + GitHub Action.

Alternatives in DevOps

  • Vercel Deploy — Deploy applications and websites to Vercel with preview or production options 14.6k ★
  • Mirrord — Run any process, on your machine or in an AI agent's environment, as if it were a pod in your Kubernetes clust 5.3k ★
  • Pagecast — Publish HTML, Markdown and static mini apps to shareable Cloudflare Pages URLs from the terminal or coding age 190 ★

README

airing logo: scarlet briefs with a keyhole, pegged on a washing line

airing

See what your deploy hangs out in public — before your agent runs it, and after it's live.
site + live demo · docs · goal

The airing laundry line: files from a sample project are pegged out one by one; the .env comes out scarlet with a tag reading PUBLIC · GOOGLE_API_KEY +3. Switching host to Netlify reels the line in and re-hangs it with the .env kept in the basket.

The problem

`wrangler pages deploy .` uploads your `.env`. So does Firebase (dotfiles are in), and Workers assets ship even `.git/`. Vercel skips `.env.local` but not `.env` or `.env.production`. **None of them read your `.gitignore`.** A coding agent that deploys "the folder that works" can publish your keys — [one leaked Gemini key cost $90k this week](https://x.com/JustLingonberry/status/2110824346168238204).

airing reads the folder the way each host's CLI actually does (rules ported from their source and cross-checked against the real libraries in CI) and tells you which secrets would sit at a public URL, plus the one change that keeps them home. Names, sizes and SHA-256 fingerprints only — it never prints a value.

Try it (10 seconds, nothing to install)

cd my-site
npx github:Blackman99/airing .
$ npx github:Blackman99/airing .
airing · Cloudflare Pages · ./  (package.json scripts.deploy)
  15 files go public · 7 stay home

   LEAK  .env                           314 B    env file — 5 variables, 4 look secret
         GOOGLE_API_KEY     Google Cloud / Gemini  AIza…(39 chars)         sha256:1aa0cc79
                            rotate → https://console.clou