← ClaudeAtlas

github-cloudflare-shiplisted

This skill should be used when the user wants to "ship this", "deploy this", "publish my code", "push to GitHub", "create a repo", "set up GitHub", "share my code", "put this online", "make this live", "get a URL for this", "host this", "I want people to see this", "deploy to Cloudflare", "how do I get this on the internet", "I want to share what I built", "make this accessible", "launch this", "push my changes", "create a repository", "set up version control", or mentions anything about getting their code online, shared, deployed, or published. This skill detects the current state of GitHub and Cloudflare configuration and only guides through what is missing. Use this skill proactively — if the user has finished building something and expresses any desire to share it, back it up, deploy it, or make it accessible, this is the right skill.
nikolanovoselec/codeflare · ★ 24 · Code & Development · score 71
Install: claude install-skill nikolanovoselec/codeflare
# Ship: From Code to Live URL An interactive, state-aware skill that guides users from zero to a live URL — detecting what is already set up and skipping completed steps. Combines GitHub setup (Phase 1) with Cloudflare Workers deployment (Phase 2). ## Target Audience Non-technical users who may have never used GitHub, git, a terminal, or deployed anything before. Every instruction must be explained in plain, jargon-free language. When technical terms are unavoidable, define them inline. ## Important: No Local Test Execution This environment has limited resources (1 CPU core). Never run `npm test` or any test suite locally. Tests only run in GitHub Actions CI, where the runner has dedicated resources. When creating CI workflows, include a test step only if the project has real tests configured. ## Shell execution (applies to every step) Every shell snippet in this skill (`gh ...`, `git ...`, `wrangler ...`, etc.) runs through the native Bash tool. Do not depend on context-mode or `ctx_*` tools; the snippet bodies in this file must work unchanged when context-mode is absent. Other runtimes should use their equivalent shell tool. User-paste blocks (where the user pastes a command into a *second terminal tab* to keep secrets off the chat) are unaffected by either path — those commands run in the user's own shell, not yours. ## Workflow On invocation, run through each step below in order. For each step, **detect the current state first** — if the step is already complete