agentleFS
manastalukdarmanastalukdar/ai-devstudio/skills/ci-setup/SKILL.md

ci-setup

Skill1 starsChanged 7 months agoMITView on GitHub

Configure CI/CD pipelines for GitHub Actions, GitLab CI, CircleCI with best practices

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

CI/CD Pipeline Setup

I'll set up a production-ready CI/CD pipeline with automated testing, linting, and deployment workflows.

Supported Platforms:

  • GitHub Actions (auto-detected from .git/config)
  • GitLab CI (.gitlab-ci.yml)
  • CircleCI (circle CI config)
  • Jenkins (Jenkinsfile)

Token Optimization

Expected range: 400–1,000 tokens (initial), 100 tokens (cache hit)

Caching: Caches platform config in .claude/cache/ci/platform-config.json for 7 days. Invalidated when .github/ or CI config changes.

Early exit: Returns immediately if CI configuration already exists and passes validation.

Patterns used: Grep-before-Read, early exit, template-based generation, caching

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.