Group
  • Deployment

    Set up a real CI/CD pipeline for my app

    Automate tests, builds, and deploys so shipping isn't a manual ritual you skip when tired.

    • Ship faster
    • Automate workflows
    • Intermediate
    • General

Free Prompt

Set up a CI/CD pipeline for my app. Right now I deploy by hand (or by pushing straight to main and hoping), which is how bugs escape and rollbacks turn into rescue missions. Build the pipeline in stages: 1. On every pull request: install dependencies, lint, run the full test suite, and build the app. Fail the PR if any step fails. Use dependency caching so this stays fast. 2. On merge to main: build a deployable artifact, run any migrations against a staging database, deploy to staging, and run smoke tests against the deployed staging URL. 3. On tag or manual approval: deploy the same artifact (not a rebuild) to production, run production smoke tests, and post the result to a channel or webhook I actually read. 4. Store secrets in the CI provider's secret store, never in the repo. Use least-privilege deploy credentials that can only deploy, not delete infrastructure. 5. Give me a green/red status badge and a clear log for every run so failures are diagnosable without me pinging you. Don't invent a bespoke shell-script pipeline; use the standard config format for whichever CI provider I'm on (GitHub Actions, GitLab CI, etc.) and ask me which if unclear. The deliverable is the pipeline config committed to the repo, documented environment variables and secrets, and one successful end-to-end run from PR to production deploy.

What This Does / How This Helps

This turns 'deploying' from a manual habit into a repeatable pipeline: PRs get tested automatically, main gets deployed to staging with smoke tests, and production ships from the same artifact after a smoke-tested staging run. Manual deploys are where launches go to die. You skip the test run because you're tired, ship a build that worked on your laptop but not in production, and then can't tell whether the fix worked because there's no repeatable process to compare against. A basic pipeline costs an afternoon and pays back the first time it catches a broken migration before it hits real users.

Want to skip doing this by hand?

Fortivibe audits your app for all of the areas these prompts cover (and more).

See What We Check

Related Prompts