pre-deploy
Skill0 starsChanged 49 days agoMITView on GitHub
Quality gate that auto-fires before "deploy", "push", "ship it", "release", or "put it in production" — runs static analysis, import/dependency checks, and tests, and only then allows the deploy.
- Reads credentials
5 other projects use a version of this.
Adopted by
Most recently taken up by
- mdigital94/vibe-shield-plugintheir own version, first seen Nov 8, 2026
- robritacca-dotcom/rift-dstheir own version, first seen Nov 1, 2026
- robritacca-dotcom/design-systemtheir own version, first seen Oct 28, 2026
- Valeriy1980/claude-skillstheir own version, first seen Oct 13, 2026
- JoviDeCroock/prachttheir own version, first seen Oct 11, 2026
Used with
Projects with it also use security-audit.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CloudflareSkillsecurity-audit
Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.
Also in 3 projects that use this
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- JoviDeCroock/pracht★ 106same name
- robritacca-dotcom/rift-ds★ 9same name
- robritacca-dotcom/design-system★ 1same name
- mdigital94/vibe-shield-plugin★ 0same name
- Valeriy1980/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- analysis-sweepSkill
- cloud-run-job-deploySkill
- grillingSkill
- self-auditSkill
- systematic-debuggingSkill
- tddSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Run the unit tests if they exist.
- Distinctive: line 27
If they don't: call the changed function at least once.
- Distinctive: line 39
If the project ships an integrated pre-deploy script (lint+test+build in one), run that — it supersedes gates 1–3.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pre-Deploy Checklist
Pass every gate below before any deploy/push/release. One failure = stop the deploy and fix first.
1. Static analysis, per language
- Python:
python -m py_compileon every changed file, plus a smoke import of the changed modules. - TypeScript/JavaScript:
npx tsc --noEmit(TS) and/or the project linter. - Match the production runtime version. Syntax that parses on your local interpreter can be a SyntaxError on the production one — compile-check with the version production actually runs.
2. Imports and dependencies
- Is every newly added import actually installed?
- Are
requirements.txt/package.jsonconsistent with the code? - Watch for missing standard-library imports (
sys,os, …) — the classic cause of a redeploy that a green linter did not catch.
3. Tests
- Run the unit tests if they exist.
- If they don't: call the changed function at least once; for an API endpoint, hit it locally with curl/httpie.
4. Env vars and secrets
.envcomplete for the target environment?- Platform wiring present (secret-manager entries, runtime service config)?
5. Final diff review
git diff --stat: no unintended files in the change.- The commit message actually describes the change.
Project-specific runner
If the project ships an integrated pre-deploy script (lint+test+build in one), run that — it supersedes gates 1–3. Never bypass pre-push hooks.
After all gates pass
Report "pre-deploy checks passed" first, then deploy. Never interleave the two.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.