setup-deploy
Skill1 starsChanged 5 months agoMITView on GitHub
Set up the Vercel project, wire environment variables across environments, and add a GitHub Actions CI workflow (lint, typecheck, build). Presents the full config plan before touching anything.
- Reads credentials
- Commits and pushes
30 other projects use a version of this.
Adopted by
Most recently taken up by
- timurgaleev/vibestacktheir own version, first seen Nov 8, 2026
- trungtm78/ClaudeSkillstheir own version, first seen Oct 25, 2026
- ignavm1/claude-skillstheir own version, first seen Oct 13, 2026
- leishifu666/skillstheir own version, first seen Oct 9, 2026
- chriswestt/claude-skillstheir own version, first seen Oct 9, 2026
- IyedBecheikh/bstacktheir own version, first seen Oct 9, 2026
Used with
Projects with it also use ios-sync, open-gstack-browser and 10 more.
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.
Saqlain-811Skillios-sync
Regenerate the iOS debug bridge against the latest upstream gstack templates. (gstack)
Also in 6 projects that use this
seek888Skillopen-gstack-browser
Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".
Also in 10 projects that use this
ShreyRaviSkilllanding-report
Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)
Also in 9 projects that use this
- ShreyRaviSkill
setup-gbrain
Set up gbrain for this coding agent: install the CLI, initialize a local PGLite or Supabase brain, register MCP, capture per-remote trust policy. One command from zero to "gbrain is running, and this agent can call it." Use when: "setup gbrain", "connect gbrain", "start gbrain", "install gbrain", "configure gbrain for this machine". (gstack)
Also in 7 projects that use this
- Saqlain-811Skill
ios-clean
Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)
Also in 5 projects that use this
- seek888Skill
pair-agent
Pair a remote AI agent with your browser. One command generates a setup key and prints instructions the other agent can follow to connect. Works with OpenClaw, Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent gets its own tab with scoped access (read+write by default, admin on request). Use when asked to "pair agent", "connect agent", "share browser", "remote browser", "let another agent use my browser", or "give browser access". (gstack) Voice triggers (speech-to-text aliases): "pair agent", "connect agent", "share my browser", "remote browser access".
Also in 11 projects that use this
- +3 more from ShreyRavi
- +1 more from Saqlain-811
Other versions30 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 30
- garrytan/gstack★ 141ksame name
- mr-daedalium/ostack-saas★ 108same name
- no-session/pstack★ 96same name
- lucas-flatwhite/gstack-ko★ 45same name
- CarbeneAI/Forge★ 9same name
- Samin12/skills★ 8same name
- timurgaleev/vibestack★ 8same name
- aryaniyaps/dot-ai★ 1same name
- chloropine/cgstack★ 1same name
- IyedBecheikh/bstack★ 1same name
20 more not listed
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 repository22 other files it gives its agents.
- build-featureSkill
- code-reviewSkill
- compliance-checkSkill
- design-architectureSkill
- design-pricingSkill
- design-schemaSkill
- design-uiSkill
- helpSkill
- launch-checklistSkill
- map-flowsSkill
- qa-planSkill
- scope-checkSkill
- security-auditSkill
- setup-billingSkill
- setup-stackSkill
- startSkill
- studio-statusSkill
- test-setupSkill
- threat-modelSkill
- validate-ideaSkill
- write-prdSkill
- write-testsSkill
The file
Files
Configure the project for production deployment on Vercel and add a GitHub Actions CI pipeline that catches regressions before merge. Non-autonomous: the full configuration plan is presented and approved before any files are written or CLI commands are run.
Phases
- Check prerequisites — verify the Vercel CLI is installed (
vercel --version) and the user is logged in (vercel whoami). Check that a GitHub remote exists (git remote -v). Confirm the target Vercel team/org and project name. If any prerequisite is missing, provide the exact setup command and wait for the user to resolve it. - Present the deployment plan — describe what will be done: (a)
vercel linkto create or connect the Vercel project, (b) environment variable wiring fordevelopment,preview, andproductionenvironments using the keys from.env.example, (c) a GitHub Actions workflow file at.github/workflows/ci.ymlwith lint, typecheck, and build jobs. Show the proposed workflow YAML verbatim for approval before writing. - Write the CI workflow — write
.github/workflows/ci.ymlwith three jobs:lint(runseslint),typecheck(runstsc --noEmit), andbuild(runsnext build). Useactions/checkout@v4,actions/setup-node@v4withnode-version-file: .nvmrcorpackage.jsonengines. Cachenode_moduleswithactions/cache. Show the file before writing. - Configure Vercel project — run
vercel link(non-interactive if possible), then walk the user through setting each required environment variable in Vercel for each environment. Provide the exactvercel env addcommands; the user must supply the actual secret values — never prompt the user to paste secrets into the conversation. - Verify CI — present the exact
git commitandgit pushcommands that will be run (including branch name and commit message) and wait for the user's explicit approval before executing either. Only after approval: commit the workflow file, push to a branch, and confirm the GitHub Actions run appears. If it fails, diagnose and propose a fix. Honor the review intensity: underfull, walk through each configuration step for sign-off; underlean, get a single confirmation before running commands; undersolo, proceed and summarize after. - Next step — point to
/launch-checklistas the final gate before going live.
Output
.github/workflows/ci.yml + Vercel project configuration. No command runs without approval.
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.