agentleFS
Sign inStart free
daemon-blockint-techdaemon-blockint-tech/Agentic-Enteprises-Skill/cicd-engineer/SKILL.md

cicd-engineer

Skill8 starsChanged 6 months agoMITView on GitHub

Guides CI/CD for agent skills repositories and skill packages—pipeline design (build, test, validate, package), GitHub Actions for PR checks and release promotion, environment gates, secrets hygiene (no secrets in repo), skill-creator integration (quick_validate.py, package_skill.py), .skill artifact strategy, rollback, and operational runbooks for skill releases. Use when the user mentions CI/CD, CI/CD engineer, pipeline design, GitHub Actions, skill validation CI, package skills, release pipeline, deploy skills, PR checks, continuous integration, or skill release workflow—not application-only CI without skill packaging (devops), pre-flight plan go/no-go (build-validator), IDP or golden paths (platform-engineer), org-wide SLO and error-budget programs without pipeline ownership (site-reliability-engineer), or portfolio catalog governance without pipeline YAML (ai-skill-manager).

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add or fix GitHub Actions workflows for skill folders, changed-path detection, and matrix validation

    line 21
  2. Distinctive:

    Document secrets, OIDC, and fork-safe PR checks for skill repos

    line 25
  3. Distinctive:

    Write rollback and change-management steps for a bad skill release

    line 26
  4. Very specific:

    Use paths / paths-filter for /SKILL.md and references/

    line 74
  5. Distinctive:

    Do not package every skill on every PR unless releasing a bundle

    line 102

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CI/CD Engineer

When to Use

  • Design or implement CI/CD for a skills monorepo (validate on PR, package on release)
  • Add or fix GitHub Actions workflows for skill folders, changed-path detection, and matrix validation
  • Wire skill-creator scripts (quick_validate.py, package_skill.py) into pipelines
  • Define quality gates: frontmatter, description length, reference layout, batch validate
  • Plan release and promotion for .skill artifacts (tags, environments, changelogs)
  • Document secrets, OIDC, and fork-safe PR checks for skill repos
  • Write rollback and change-management steps for a bad skill release
  • Produce runbooks for on-call during skill publish failures

When NOT to Use

  • Application/service CI only (containers, K8s deploy, app test suites) without skill packaging → devops
  • Pre-flight architecture or build go/no-go before execution → build-validator
  • Internal developer platform, golden paths, Backstage, paved-road templates → platform-engineer
  • SLI/SLO programs, error budgets, burn-rate alerting, PRR without pipeline work → site-reliability-engineer
  • Skill catalog inventory, overlap dedup, deprecate/split governance without CI YAML → ai-skill-manager
  • Security gates (SBOM, SAST policy, supply-chain signing) as the primary task → devsecops
  • Author a single new skill from scratch (content only) → skill-creator / init_skill.py

Related skills

NeedSkill
General app CI/CD, GitOps, container deliverydevops
Go/no-go validation before major changesbuild-validator
IDP, golden paths, developer portalplatform-engineer
SLOs, reliability metrics, incident reliabilitysite-reliability-engineer
Batch validate script, portfolio standardsai-skill-manager
Pipeline and artifact security gatesdevsecops
Release cutover tiers and change windowsdeployment-strategist

Core Workflows

1. Pipeline topology for skills repos

Standard stage order:

checkout → detect changed skills → validate (quick_validate) → optional lint/scripts → package on release tag → publish artifact → notify

Checklist:

  • Pipeline as code under .github/workflows/; versioned with repo
  • PR jobs run on changed skill directories only when possible
  • quick_validate.py gates merge; fail closed on invalid frontmatter
  • Release job runs package_skill.py only after validation passes
  • Artifacts immutable (tag + commit SHA in name or metadata)
  • Manual or environment approval before org-wide distribution

See references/pipeline_design_and_workflow.md.

2. GitHub Actions implementation

  1. Use paths / paths-filter for **/SKILL.md and references/**
  2. Matrix or loop per changed skill directory
  3. Cache nothing sensitive; use GITHUB_TOKEN with least scope
  4. Fork PRs: read-only checks; no secrets on pull_request_target without hardening
  5. Reusable workflow (workflow_call) for validate + package jobs

See references/github_actions_and_build.md.

3. Testing and quality gates

GateTool / check
Structure + YAMLquick_validate.py
Batch regressionai-skill-manager/scripts/validate_all_skills.sh
Description triggersHuman review + grep for duplicate keywords
Scripts in skill dirsLint + no network exfil patterns

See references/testing_gates_and_quality.md.

4. Skill validation and packaging CI

python3 ~/.claude/skills/skill-creator/scripts/quick_validate.py path/to/skill-dir
python3 ~/.claude/skills/skill-creator/scripts/package_skill.py path/to/skill-dir ./dist
  • PR: validate changed skills only
  • Release: package validated skills; attach .skill to GitHub Release or internal registry
  • Do not package every skill on every PR unless releasing a bundle

See references/skill_validation_and_packaging_ci.md.

5. Deployment, promotion, and operations

  1. Dev/staging: auto-validate on PR merge to main
  2. Release: tag skill-v* or calendar version; package and publish
  3. Promotion: copy artifacts to consumer paths (plugin cache, internal registry) with checksum
  4. Rollback: re-publish previous tag artifacts; document superseded skill description if needed
  5. Runbook: who approves, how to verify install, comms for broken bundle

See references/deployment_promotion_and_operations.md.

6. Scope and boundaries

Confirm the ask is skills-repo CI/CD, not generic platform ops. Load references/cicd_engineer_scope.md when routing or scoping engagements.

When to load references

TopicReference
Role boundaries and triggersreferences/cicd_engineer_scope.md
Pipeline stages, branching, artifactsreferences/pipeline_design_and_workflow.md
GitHub Actions patternsreferences/github_actions_and_build.md
Gates, batch validate, PR policyreferences/testing_gates_and_quality.md
quick_validate / package_skill in CIreferences/skill_validation_and_packaging_ci.md
Release, promotion, rollback, runbooksreferences/deployment_promotion_and_operations.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free