How do I install the Config Cicd skill?

Run npx skillmds@latest add eskcti/config-cicd in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Config Cicd safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Config Cicd?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Config Cicd free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Config Cicd?

EskCti (@eskcti) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Config Cicd by eskcti — Agent Skill

Name: Config Cicd
Author: EskCti

Config Cicd

Criar ou revisar pipeline GitHub Actions para projetos TypeScript (NestJS + Next.js), cobrindo lint, testes unitários, build Docker, push para registry e deploy. Usar quando o pedido envolver GitHub Actions, CI/CD, pipeline, workflow, deploy automatizado ou configuração de integração contínua para stack TypeScript/NestJS/Next.js.

EskCti Updated Sep 21, 2026

File contents

Config CI/CD (TypeScript)

Overview

Gerar workflows GitHub Actions para monorepo TurboRepo com NestJS backend e Next.js frontend, cobrindo CI (lint + test + coverage gate ≥95% domain/application + build) e CD (build Docker + push + deploy).

Estrutura gerada

project-root/
├── scripts/
│   └── check-coverage.mjs  ← gate ≥95% domain+application
└── .github/
    └── workflows/
        ├── ci.yml          ← lint + test + coverage gate
        └── cd.yml          ← build Docker + push + deploy

Workflow

Verificar se .github/workflows/ existe; criar se necessário.
Copiar assets/check-coverage.mjs deste skill para scripts/check-coverage.mjs no projeto.
Criar ci.yml — executado em PRs e pushes para branches de feature.
Criar cd.yml — executado em push para main ou tags v*.
Perguntar ao usuário: registry de destino (GHCR, Docker Hub, ECR)?
Perguntar: ambiente de deploy (Fly.io, Railway, ECS, VPS)?
Adaptar o cd.yml com base nas respostas.

Perguntas ao usuário (antes de criar cd.yml)

"Para o pipeline de CD, preciso saber:\n> 1. Registry Docker: GitHub Container Registry (GHCR), Docker Hub, ou AWS ECR?\n> 2. Deploy para: Fly.io, Railway, AWS ECS, VPS (SSH), ou apenas build/push sem deploy automático?"

References

Consultar references/cicd-pattern.md para templates completos dos workflows.
Consultar ../skills-standards.md para convenções globais.

Global Standards

Consultar ../skills-standards.md para padrões globais de nomenclatura e convenções gerais entre skills.

---name: config-cicddescription: Criar ou revisar pipeline GitHub Actions para projetos TypeScript (NestJS + Next.js), cobrindo lint, testes unitários, build Docker, push para registry e deploy. Usar quando o pedido envolver GitHub Actions, CI/CD, pipeline, workflow, deploy automatizado ou configuração de integração contínua para stack TypeScript/NestJS/Next.js.---# Config CI/CD (TypeScript)## OverviewGerar workflows GitHub Actions para monorepo TurboRepo com NestJS backend e Next.js frontend, cobrindo CI (lint + test + **coverage gate ≥95% domain/application** + build) e CD (build Docker + push + deploy).## Estrutura gerada```project-root/├── scripts/│ └── check-coverage.mjs ← gate ≥95% domain+application└── .github/ └── workflows/ ├── ci.yml ← lint + test + coverage gate └── cd.yml ← build Docker + push + deploy```## Workflow1. Verificar se `.github/workflows/` existe; criar se necessário.2. Copiar `assets/check-coverage.mjs` deste skill para `scripts/check-coverage.mjs` no projeto.3. Criar `ci.yml` — executado em PRs e pushes para branches de feature.4. Criar `cd.yml` — executado em push para `main` ou tags `v*`.5. Perguntar ao usuário: registry de destino (GHCR, Docker Hub, ECR)?6. Perguntar: ambiente de deploy (Fly.io, Railway, ECS, VPS)?7. Adaptar o `cd.yml` com base nas respostas.## Perguntas ao usuário (antes de criar cd.yml)> "Para o pipeline de CD, preciso saber:\n> 1. Registry Docker: GitHub Container Registry (GHCR), Docker Hub, ou AWS ECR?\n> 2. Deploy para: Fly.io, Railway, AWS ECS, VPS (SSH), ou apenas build/push sem deploy automático?"## References- Consultar `references/cicd-pattern.md` para templates completos dos workflows.- Consultar `../skills-standards.md` para convenções globais.## Global Standards- Consultar `../skills-standards.md` para padrões globais de nomenclatura e convenções gerais entre skills.

Frequently asked questions