Ci

Skill KhaiTrang1995/agentic-awesome-kits/kits/devops/docker-kit/.claude/skills/ci

A universal collection of reusable Loop Engineering kits for AI coding agents—not just prompts. Each kit combines Skills, Rules, Templates, workflows, and validation loops to help agents autonomously plan, execute, verify, fix, and improve engineering tasks.

Install

npx -y skills add KhaiTrang1995/agentic-awesome-kits --skill ci

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generate a CI/CD pipeline — build, test, security scan, deploy. Supports GitHub Actions, GitLab CI, Bitbucket Pipelines.

SKILL.md

1.4 KB, as published. Nobody here has run it

/ci — Generate a CI/CD Pipeline

Input examples

/ci .NET 10 --platform bitbucket --with-scan
/ci Angular + .NET fullstack --platform github --with-deploy
/ci Python FastAPI --platform gitlab --with-scan --with-deploy

Pipeline stages

1. Build

Restore dependencies
Compile/build
Build the Docker image (if containerized)

2. Test

Unit tests + coverage report
Lint (dotnet format / eslint / ruff)

3. Security Scan (if `--with-scan`)

Dependency audit (dotnet list --vulnerable / npm audit / pip audit)
Source code security scan
Container image scan (Trivy)

4. Deploy (if `--with-deploy`)

Push image to registry
Deploy to staging (automatic)
Deploy to production (manual approval)

Output

.github/workflows/ci.yml          ← (GitHub Actions)
bitbucket-pipelines.yml            ← (Bitbucket)
.gitlab-ci.yml                     ← (GitLab)

Rules

Cache dependencies between runs
Fail fast: a failed test skips deploy
Secrets via CI/CD variables, NEVER hardcoded
Production deploy requires manual approval

References

@.claude/rules/docker-conventions.md