ci-cd-pipeline

Automate GitHub Actions CI/CD with parallel lint, typecheck, and test jobs.

1|1|Updated Apr 13, 2026

Search Tags:#workflow #deployment #rollback #github-actions #ci-cd #lint

Ready to run

npx skills add https://github.com/Cheggin/request-for-startups --skill ci-cd-pipeline-cheggin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-cd-pipeline
Source: https://github.com/Cheggin/request-for-startups/tree/main/skills/ci-cd-pipeline
Command: npx skills add https://github.com/Cheggin/request-for-startups --skill ci-cd-pipeline-cheggin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub Actions-based CI/CD automation reduces manual toil by running lint, typecheck, and tests in parallel, gating merges with health checks, and enabling staged and production deployments with automatic rollback.

Core Features & Use Cases

Parallel lint, typecheck, and tests on every push and PR to deliver fast feedback.
Staging deployments on main to Vercel, Railway, and Convex with gate protections.
Production deployments triggered by release tags, with environment-specific configurations and automatic rollback.
Health checks after deployment and automatic rollback on failure, with notifications.

Quick Start

Configure a GitHub Actions workflow to run lint, typecheck, and tests in parallel on push/PR, deploy to staging on main, and deploy to production on release tags.

Frequently Asked Questions about ci-cd-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up GitHub Actions CI/CD with automated rollback for production deployments?▼

Automate GitHub Actions CI/CD by configuring workflows to run parallel lint, typecheck, and tests, deploy to staging on main, and trigger production deployments on release tags with automatic rollback on health check failures.

What is the best way to gate merges in GitHub Actions using parallel lint and test jobs?▼

Gating merges in GitHub Actions requires running parallel lint, typecheck, and test jobs on every push and PR to deliver fast feedback and ensure code quality before allowing merges into the main branch.

Can I deploy to staging on Vercel and Railway using GitHub Actions CI/CD?▼

Yes, GitHub Actions CI/CD supports staging deployments on main to Vercel, Railway, and Convex with gate protections, ensuring environment-specific configurations and safe previews before production.

How does automatic rollback work for production deployments triggered by release tags?▼

Automatic rollback activates when post-deployment health checks fail after a production deployment triggered by a release tag, reverting the environment and sending notifications through configured channels.

Do I need release tags to deploy to production with GitHub Actions CI/CD?▼

Yes, production deployments are triggered specifically by release tags, separating them from staging deployments on the main branch and ensuring production gating and health verification before release.