Deploy Release Test
vercel/next.js
Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the teste2edeployrelease.yml GitHub Actions workflow.
Automates CI/CD pipeline setup. An agent skill from dzhalaevd/Donatello.
$ npx skills add dzhalaevd/Donatello --skill ci-cd-and-automation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dzhalaevd/Donatello ci-cd-and-automation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dzhalaevd/Donatello.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/ci-cd-and-automation .claude/skills/ci-cd-and-automation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ci-cd-and-automation" agent skill from https://github.com/dzhalaevd/Donatello/tree/main/.agents/skills/ci-cd-and-automation into .claude/skills/ci-cd-and-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-cd-and-automation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dzhalaevd/Donatello/tree/main/.agents/skills/ci-cd-and-automationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dzhalaevd/Donatello --skill ci-cd-and-automation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dzhalaevd/Donatello ci-cd-and-automation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dzhalaevd/Donatello.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/ci-cd-and-automation .agents/skills/ci-cd-and-automation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ci-cd-and-automation" agent skill from https://github.com/dzhalaevd/Donatello/tree/main/.agents/skills/ci-cd-and-automation into .agents/skills/ci-cd-and-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-cd-and-automation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dzhalaevd/Donatello --skill ci-cd-and-automation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dzhalaevd/Donatello ci-cd-and-automation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dzhalaevd/Donatello.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/ci-cd-and-automation .cursor/skills/ci-cd-and-automation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ci-cd-and-automation" agent skill from https://github.com/dzhalaevd/Donatello/tree/main/.agents/skills/ci-cd-and-automation into .cursor/skills/ci-cd-and-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-cd-and-automation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dzhalaevd/Donatello.git --path .agents/skills/ci-cd-and-automation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dzhalaevd/Donatello --skill ci-cd-and-automation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dzhalaevd/Donatello ci-cd-and-automation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dzhalaevd/Donatello.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/ci-cd-and-automation .gemini/skills/ci-cd-and-automation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ci-cd-and-automation" agent skill from https://github.com/dzhalaevd/Donatello/tree/main/.agents/skills/ci-cd-and-automation into .gemini/skills/ci-cd-and-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-cd-and-automation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dzhalaevd/Donatello ci-cd-and-automationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dzhalaevd/Donatello --skill ci-cd-and-automation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dzhalaevd/Donatello.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/ci-cd-and-automation .github/skills/ci-cd-and-automation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ci-cd-and-automation" agent skill from https://github.com/dzhalaevd/Donatello/tree/main/.agents/skills/ci-cd-and-automation into .github/skills/ci-cd-and-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-cd-and-automation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dzhalaevd/Donatello --skill ci-cd-and-automation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dzhalaevd/Donatello ci-cd-and-automation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dzhalaevd/Donatello.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/ci-cd-and-automation .opencode/skills/ci-cd-and-automation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ci-cd-and-automation" agent skill from https://github.com/dzhalaevd/Donatello/tree/main/.agents/skills/ci-cd-and-automation into .opencode/skills/ci-cd-and-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-cd-and-automation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
ci-cd-and-automationAutomates CI/CD pipeline setup. An agent skill from dzhalaevd/Donatello.
CI CD And Automation is an agent skill from dzhalaevd/Donatello. Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering CI/CD, Deployment and Quality gates. The repository describes itself as: Make Dating Great Again. An open source dating platform. The licence is Apache-2.0.
Read from SKILL.md and the folder at commit b57816e. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml and typescript).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
CI_DB_PASSWORDPOSTGRES_PASSWORDVERCEL_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
CI CD And Automation loads about 2.7k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 684 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
.env → NOT committed (local development).env.test → Committed (test environment, no real secrets)Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from dzhalaevd/Donatello at commit b57816e, republished under its Apache-2.0 licence (© dzhalaevd). 684 words, ~2,749 tokens.
.claude/skills/ci-cd-and-automation/SKILL.md (or your agent's skills folder).Automate quality gates so that no change reaches production without passing tests, lint, type checking, and build. CI/CD is the enforcement mechanism for every other skill — it catches what humans and agents miss, and it does so consistently on every single change.
Shift Left: Catch problems as early in the pipeline as possible. A bug caught in linting costs minutes; the same bug caught in production costs hours. Move checks upstream — static analysis before tests, tests before staging, staging before production.
Faster is Safer: Smaller batches and more frequent releases reduce risk, not increase it. A deployment with 3 changes is easier to debug than one with 30. Frequent releases build confidence in the release process itself.
Every change goes through these gates before merge:
Pull Request Opened
│
▼
┌─────────────────┐
│ LINT CHECK │ eslint, prettier
│ ↓ pass │
│ TYPE CHECK │ tsc --noEmit
│ ↓ pass │
│ UNIT TESTS │ jest/vitest
│ ↓ pass │
│ BUILD │ npm run build
│ ↓ pass │
│ INTEGRATION │ API/DB tests
│ ↓ pass │
│ E2E (optional) │ Playwright/Cypress
│ ↓ pass │
│ SECURITY AUDIT │ npm audit
│ ↓ pass │
│ BUNDLE SIZE │ bundlesize check
└─────────────────┘
│
▼
Ready for reviewNo gate can be skipped. If lint fails, fix lint — don't disable the rule. If a test fails, fix the code — don't skip the test.
# .github/workflows/ci.yml
name: CI
on:
pull_request:
branches: [main]
push:
branches: [main]
jobs:
quality:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '22'
cache: 'npm'
- name: Install dependencies
run: npm ci
- name: Lint
run: npm run lint
- name: Type check
run: npx tsc --noEmit
- name: Test
run: npm test -- --coverage
- name: Build
run: npm run build
- name: Security audit
run: npm audit --audit-level=high integration:
runs-on: ubuntu-latest
services:
postgres:
image: postgres:16
env:
POSTGRES_DB: testdb
POSTGRES_USER: ci_user
POSTGRES_PASSWORD: ${{ secrets.CI_DB_PASSWORD }}
ports:
- 5432:5432
options: >-
--health-cmd pg_isready
--health-interval 10s
--health-timeout 5s
--health-retries 5
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '22'
cache: 'npm'
- run: npm ci
- name: Run migrations
run: npx prisma migrate deploy
env:
DATABASE_URL: postgresql://ci_user:${{ secrets.CI_DB_PASSWORD }}@localhost:5432/testdb
- name: Integration tests
run: npm run test:integration
env:
DATABASE_URL: postgresql://ci_user:${{ secrets.CI_DB_PASSWORD }}@localhost:5432/testdbNote: Even for CI-only test databases, use GitHub Secrets for credentials rather than hardcoding values. This builds good habits and prevents accidental reuse of test credentials in other contexts.
e2e:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '22'
cache: 'npm'
- run: npm ci
- name: Install Playwright
run: npx playwright install --with-deps chromium
- name: Build
run: npm run build
- name: Run E2E tests
run: npx playwright test
- uses: actions/upload-artifact@v4
if: failure()
with:
name: playwright-report
path: playwright-report/The power of CI with AI agents is the feedback loop. When CI fails:
CI fails
│
▼
Copy the failure output
│
▼
Feed it to the agent:
"The CI pipeline failed with this error:
[paste specific error]
Fix the issue and verify locally before pushing again."
│
▼
Agent fixes → pushes → CI runs againKey patterns:
Lint failure → Agent runs `npm run lint --fix` and commits
Type error → Agent reads the error location and fixes the type
Test failure → Agent follows diagnosing-bugs skill
Build error → Agent checks config and dependenciesEvery PR gets a preview deployment for manual testing:
# Deploy preview on PR (Vercel/Netlify/etc.)
deploy-preview:
runs-on: ubuntu-latest
if: github.event_name == 'pull_request'
steps:
- uses: actions/checkout@v4
- name: Deploy preview
run: npx vercel --token=${{ secrets.VERCEL_TOKEN }}Feature flags decouple deployment from release. Deploy incomplete or risky features behind flags so you can:
// Simple feature flag pattern
if (featureFlags.isEnabled('new-checkout-flow', { userId })) {
return renderNewCheckout();
}
return renderLegacyCheckout();Flag lifecycle: Create → Enable for testing → Canary → Full rollout → Remove the flag and dead code. Flags that live forever become technical debt — set a cleanup date when you create them.
PR merged to main
│
▼
Staging deployment (auto)
│ Manual verification
▼
Production deployment (manual trigger or auto after staging)
│
▼
Monitor for errors (15-minute window)
│
├── Errors detected → Rollback
└── Clean → DoneEvery deployment should be reversible:
# Manual rollback workflow
name: Rollback
on:
workflow_dispatch:
inputs:
version:
description: 'Version to rollback to'
required: true
jobs:
rollback:
runs-on: ubuntu-latest
steps:
- name: Rollback deployment
run: |
# Deploy the specified previous version
npx vercel rollback ${{ inputs.version }}.env.example → Committed (template for developers)
.env → NOT committed (local development)
.env.test → Committed (test environment, no real secrets)
CI secrets → Stored in GitHub Secrets / vault
Production secrets → Stored in deployment platform / vaultCI should never have production secrets. Use separate secrets for CI testing.
# .github/dependabot.yml
version: 2
updates:
- package-ecosystem: npm
directory: /
schedule:
interval: weekly
open-pull-requests-limit: 5Designate someone responsible for keeping CI green. When the build breaks, the Build Cop's job is to fix or revert — not the person whose change caused the break. This prevents broken builds from accumulating while everyone assumes someone else will fix it.
When the pipeline exceeds 10 minutes, apply these strategies in order of impact:
Slow CI pipeline?
├── Cache dependencies
│ └── Use actions/cache or setup-node cache option for node_modules
├── Run jobs in parallel
│ └── Split lint, typecheck, test, build into separate parallel jobs
├── Only run what changed
│ └── Use path filters to skip unrelated jobs (e.g., skip e2e for docs-only PRs)
├── Use matrix builds
│ └── Shard test suites across multiple runners
├── Optimize the test suite
│ └── Remove slow tests from the critical path, run them on a schedule instead
└── Use larger runners
└── GitHub-hosted larger runners or self-hosted for CPU-heavy buildsExample: caching and parallelism
jobs:
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with: { node-version: '22', cache: 'npm' }
- run: npm ci
- run: npm run lint
typecheck:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with: { node-version: '22', cache: 'npm' }
- run: npm ci
- run: npx tsc --noEmit
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with: { node-version: '22', cache: 'npm' }
- run: npm ci
- run: npm test -- --coverage| Rationalization | Reality |
|---|---|
| "CI is too slow" | Optimize the pipeline (see CI Optimization below), don't skip it. A 5-minute pipeline prevents hours of debugging. |
| "This change is trivial, skip CI" | Trivial changes break builds. CI is fast for trivial changes anyway. |
| "The test is flaky, just re-run" | Flaky tests mask real bugs and waste everyone's time. Fix the flakiness. |
| "We'll add CI later" | Projects without CI accumulate broken states. Set it up on day one. |
| "Manual testing is enough" | Manual testing doesn't scale and isn't repeatable. Automate what you can. |
After setting up or modifying CI:
© dzhalaevd, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/ci-cd-and-automation of dzhalaevd/Donatello.
Open the folder on GitHubat commit b57816e
We found 15 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 7 other GitHub owners. This page covers the copy in dzhalaevd/Donatello, which our catalogue first saw on October 7, 2026.
CI CD And Automation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| CI CD And Automation this skilldzhalaevd/Donatello | 135 | 7 repos | ~2.7k | Automated safety check: Notes | Apache-2.0 | |
| Deploy Release Testvercel/next.js | 143k | — | ~1.2k | Automated safety check: Pass | MIT | |
| OpenWork Release Validationdifferent-ai/openwork | 24k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Bmad Testarch CIbmad-code-org/bmad-method-test-architecture-enterprise | 105 | 3 repos | ~449 | Automated safety check: Pass | Custom licence | |
| Bmad Tea Testarch CIchenjackle45/SayIt | 115 | — | ~226 | Automated safety check: Pass | MIT | |
| Agents Optimizeaws/agent-toolkit-for-aws | 2.8k | — | ~914 | Automated safety check: Notes | Apache-2.0 |
vercel/next.js
Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the teste2edeployrelease.yml GitHub Actions workflow.
different-ai/openwork
Checks a published OpenWork desktop release by booting the released macOS binaries through packaged journeys, verifying signing and updater manifests, and publishing evidence.
bmad-code-org/bmad-method-test-architecture-enterprise
Scaffold CI/CD quality pipeline with test execution. An agent skill from bmad-code-org/bmad-method-test-architecture-enterprise.
chenjackle45/SayIt
Scaffold CI/CD quality pipeline with test execution. An agent skill from chenjackle45/SayIt.
aws/agent-toolkit-for-aws
A skill your agent uses when measuring or improving agent quality and performance — set up evaluators, online monitoring, CI/CD quality gates, observability, or cost optimization.
jeremylongshore/tons-of-skills-marketplace
Configure CI/CD pipelines for Apify Actor builds and deployments.
dzhalaevd/Donatello
Guides stable API and interface design. An agent skill from dzhalaevd/Donatello.
dzhalaevd/Donatello
Records decisions and documentation. An agent skill from dzhalaevd/Donatello.
dzhalaevd/Donatello
Manages deprecation and migration. An agent skill from dzhalaevd/Donatello.
dzhalaevd/Donatello
Instruments code so production behavior is visible and diagnosable.
dzhalaevd/Donatello
Prepares production launches. An agent skill from dzhalaevd/Donatello.
dzhalaevd/Donatello
Optimizes application performance across frontend, backend, queries, and databases.
Categories
Automates CI/CD pipeline setup. An agent skill from dzhalaevd/Donatello. CI CD And Automation is an agent skill from dzhalaevd/Donatello. Automates CI/CD pipeline setup.
CI CD And Automation fits situations like: modifying build and deployment pipelines; you need to automate quality gates; configure test runners in CI; establish deployment strategies.
Run `npx skills add dzhalaevd/Donatello --skill ci-cd-and-automation -a claude-code`. Or copy the skill folder (.agents/skills/ci-cd-and-automation in dzhalaevd/Donatello) into .claude/skills/ci-cd-and-automation in your project. Claude Code loads it when a task matches its description.
Run `npx skills add dzhalaevd/Donatello --skill ci-cd-and-automation -a codex`. Or copy the skill folder (.agents/skills/ci-cd-and-automation in dzhalaevd/Donatello) into .agents/skills/ci-cd-and-automation in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dzhalaevd/Donatello --skill ci-cd-and-automation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ci-cd-and-automation, .gemini/skills/ci-cd-and-automation, .github/skills/ci-cd-and-automation and .opencode/skills/ci-cd-and-automation in your project.
Going by SKILL.md and its folder, CI CD And Automation needs credentials named CI_DB_PASSWORD, POSTGRES_PASSWORD and VERCEL_TOKEN. Our summary lists: Node.js; A credential in VERCEL_TOKEN.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
CI CD And Automation is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with CI CD And Automation: Deploy Release Test (vercel/next.js, 143k stars), OpenWork Release Validation (different-ai/openwork, 24k stars), Bmad Testarch CI (bmad-code-org/bmad-method-test-architecture-enterprise, 105 stars) and Bmad Tea Testarch CI (chenjackle45/SayIt, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
dzhalaevd (a GitHub user) maintains it in dzhalaevd/Donatello, which has 135 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 3, 2026.
Source: dzhalaevd/Donatello on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.