7 claude code slash commands i run before anything goes live

elisabeth hitz · july 27, 2026 · 3 min read

i ship alone. 75+ live sites, no engineering team, no CS degree. the reason that works is not talent, it's gates: commands that check my work before and after every ship. these seven are real files in my ~/.claude/skills/ folder.

1. /pre-deploy-file-count-gate

refuses to deploy if files went missing since the last version. sounds paranoid until the day a build silently drops half a folder and you ship a skeleton. the gate catches it before the internet does.

2. /deploy-with-history-check

compares what's about to go live against what's currently live and surfaces the divergence. no deploy happens without checking what is already live first.

3. /post-deploy-health-check

"deploy succeeded" and "site works" are two different sentences. this one loads the live site after every deploy and confirms the second one.

4. /verify-funnel-e2e

walks the entire money path: page loads, form fires, the subscriber lands in Kit with the right tag, the sequence enrolls, the stripe links resolve. funnels don't break loudly. they break silently and pay you nothing for weeks. this is the smoke detector.

5. /pricing-cleanse

sweeps pages for every price mention and flags the ones that do not belong where they sit. stray price tags and old launch banners are how a site quietly contradicts itself. i learned this one from my own site.

6. /claim-check

the fact gate for content. every number, every "proven", every "data shows" needs a source or the draft doesn't publish. built after my own AI confidently presented me an audit that never happened.

7. /emergency-rollback

the undo button. it finds the last known-good deploy and restores it in seconds. i almost never need it, and it's the reason i can ship fast without fear.

the pattern

none of these are clever. each one is a rule i was already supposed to follow, converted into a file that follows it for me. gate before. check after. rollback ready.

that architecture, rules as files instead of intentions, is the whole thing i teach. the toolkit is 27 skills built this way for the business side: voice, offers, content, launch. and if you're wondering whether your current AI stack would survive this kind of scrutiny, the hype detector will tell you in 90 seconds.

go deeper

source: the seven live skill files in ~/.claude/skills this post describes; every description above checked against the actual SKILL.md before publish, july 27 2026. written by elisabeth hitz, certified in anthropic's ai fluency program (framework & foundations, and ai capabilities & limitations), plus claude 101 and claude cowork.