agentleFS
Tony363Tony363/SuperClaude/.claude/skills/sc-cicd-setup/SKILL.md

sc-cicd-setup

Skill19 starsChanged 8 months agoMITView on GitHub

Bootstrap GitHub CI/CD workflows and pre-commit hooks for any project using battle-tested templates. After running, you may need to: 1. Add ANTHROPIC_API_KEY secret for AI review 2. Run pre-commit install to enable hooks 3. Add PYPI_API_TOKEN / NPM_TOKEN / CARGO_REGISTRY_TOKEN for publishing 4. Add CODECOV_TOKEN for coverage reporting Templates are in templates/workflows/{python,node,go,rust}/: - ci.yml.j2 - Main CI pipeline - security.yml.j2 - Security scanning - ai-review.yml.j2 - AI code review - publish.yml.j2 - Package publishing - pre-commit-config.yaml.j2 - Pre-commit hooks

  • 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

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Validate: check for existing files

    line 61
  2. Distinctive:

    After running, you may need to:

    line 88
  3. Very specific:

    Add ANTHROPIC_API_KEY secret for AI review

    line 89
  4. Very specific:

    Run pre-commit install to enable hooks

    line 90
  5. Very specific:

    Add PYPI_API_TOKEN / NPM_TOKEN / CARGO_REGISTRY_TOKEN for publishing

    line 91
  6. Very specific:

    Add CODECOV_TOKEN for coverage reporting

    line 92

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

SC:CICD-Setup Skill

Bootstrap GitHub CI/CD workflows and pre-commit hooks for any project using battle-tested templates.

When to Use

  • Setting up a new project with CI/CD
  • Adding GitHub Actions to an existing repository
  • Standardizing CI/CD across multiple projects
  • User requests: "set up CI", "add GitHub Actions", "configure pipelines"

Invocation

/sc:cicd-setup [--lang <language>] [--yes] [--force] [--minimal|--full]

Flags

FlagDescription
--langForce project language: python, node, go, rust
--yesAccept defaults, skip confirmation prompts
--forceOverwrite existing workflow files (backs up originals)
--minimalOnly essential CI workflow
--fullAll workflows including publish/release

Supported Languages

Python

  • CI: ruff lint/format, mypy, pytest, coverage
  • Security: CodeQL, pip-audit, Bandit
  • AI Review: Claude-powered PR review
  • Publish: PyPI release automation
  • Pre-commit: ruff, mypy, bandit hooks

Node.js

  • CI: ESLint, tests, build
  • Security: npm audit, CodeQL
  • AI Review: Claude-powered PR review
  • Publish: npm publish automation
  • Pre-commit: ESLint, Prettier hooks

Go

  • CI: go vet, golangci-lint, tests, cross-compile
  • Security: gosec, govulncheck, CodeQL
  • AI Review: Claude-powered PR review
  • Pre-commit: gofmt, golangci-lint hooks

Rust

  • CI: rustfmt, clippy, tests, cross-compile
  • Security: cargo-audit, cargo-deny
  • AI Review: Claude-powered PR review
  • Publish: crates.io automation
  • Pre-commit: rustfmt, clippy hooks

Workflow

  1. Detect project type from manifest files
  2. Configure based on flags (minimal/full/default)
  3. Validate check for existing files
  4. Present summary of what will be created
  5. Confirm (skip with --yes)
  6. Generate workflow files from templates
  7. Report next steps

Examples

# Auto-detect and setup (interactive)
/sc:cicd-setup

# Python project, non-interactive
/sc:cicd-setup --lang python --yes

# Full suite with publish workflow
/sc:cicd-setup --full

# Minimal CI only
/sc:cicd-setup --minimal

# Force overwrite existing
/sc:cicd-setup --force

Post-Setup

After running, you may need to:

  1. Add ANTHROPIC_API_KEY secret for AI review
  2. Run pre-commit install to enable hooks
  3. Add PYPI_API_TOKEN / NPM_TOKEN / CARGO_REGISTRY_TOKEN for publishing
  4. Add CODECOV_TOKEN for coverage reporting

Template Location

Templates are in templates/workflows/{python,node,go,rust}/:

  • ci.yml.j2 - Main CI pipeline
  • security.yml.j2 - Security scanning
  • ai-review.yml.j2 - AI code review
  • publish.yml.j2 - Package publishing
  • pre-commit-config.yaml.j2 - Pre-commit hooks

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.