One-click install
npx skills add https://github.com/johinsDev/loyalty-app --skill ci-cd-johinsdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-cd
Source: https://github.com/johinsDev/loyalty-app/tree/main/.claude/skills/ci-cd
Command: npx skills add https://github.com/johinsDev/loyalty-app --skill ci-cd-johinsdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

CI/CD setups often cause confusion about what runs where (validation vs deployment), leading to broken builds, insecure handling of sensitive environment variables, and inconsistent release quality.

Core Features & Use Cases

  • PR-guarded, validate-only GitHub Actions: Runs lint, dead-code detection, typechecking, and tests on every push/PR to keep main stable.
  • Vercel Git integration for deployment: Uses Vercel’s native Git watching so Preview and Production deploys are triggered consistently without trying to decrypt sensitive vars in CI.
  • Branch protection and workflow enforcement: Ensures required status checks (the validate job suite) must pass before merging.
  • Troubleshooting for common failure modes: Covers lockfile drift, cache-related discrepancies, missing Vercel env vars, and workflow/branch-protection mismatches.

Quick Start

Use the ci-cd skill to guide a PR that adds or debugs a CI check by editing .github/workflows/ci.yml, then confirming the required validate (lint, knip, typecheck, test) status checks show up and pass before merging.

Frequently Asked Questions about ci-cd

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

FAQPage Schema
How do I configure GitHub Actions to run validation only without handling Vercel deployments?

Configure GitHub Actions to run validate-only jobs like lint, knip, typecheck, and test on every PR, while delegating actual deployments to Vercel's native Git integration to prevent pipeline breakage from sensitive environment variables.

Why do my CI builds fail when trying to access Vercel sensitive environment variables?

CI builds fail because decrypting sensitive environment variables during pipeline execution causes breakage; avoid Vercel sensitive env var access during CI builds and rely on Vercel's Git integration to handle Preview and Production deploys independently.

What branch protection rules are needed for a Next.js monorepo CI workflow?

Branch protection requires enforcing main-only merging by setting the validate job suite, which runs lint, knip, typecheck, and test, as required status checks that must pass before any pull request can be merged.

How do I troubleshoot lockfile drift and cache discrepancies in GitHub Actions pipelines?

Troubleshoot lockfile drift and cache-related discrepancies by standardizing your validate-only CI workflow, ensuring consistent dependency installation, and verifying that branch protection configurations match your workflow status checks.

Can I use Vercel Git integration for deployment while keeping GitHub Actions strictly for validation?

Yes, you can use Vercel's native Git watching to trigger Preview and Production deploys consistently, while restricting GitHub Actions CI to validation tasks like lint, dead-code detection, typechecking, and tests to keep main stable.

What validation steps should I include in a monorepo pull request gating workflow?

A monorepo pull request gating workflow should include lint, dead-code detection using knip, typechecking, and tests as required validate jobs to ensure code quality before merging changes into the main branch.