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
- kreighmitchell/SuperClaudeword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- kreighmitchell/SuperClaude★ 4100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-data-engineerSkill
- agent-fullstack-developerSkill
- agent-kubernetes-specialistSkill
- agent-ml-engineerSkill
- agent-performance-engineerSkill
- agent-react-specialistSkill
- agent-security-engineerSkill
- agent-technical-writerSkill
- ask-multiSkill
- askSkill
- learned-skills-indexSkill
- sc-analyzeSkill
- sc-brainstormSkill
- sc-buildSkill
- sc-code-reviewSkill
- sc-designSkill
- sc-documentSkill
- sc-e2eSkill
- sc-estimateSkill
- sc-evaluateSkill
- sc-explainSkill
- sc-gitSkill
- sc-implementSkill
- sc-improveSkill
- sc-log-fixSkill
- sc-mcpSkill
- sc-pr-checkSkill
- sc-pr-fixSkill
- sc-principlesSkill
- sc-pushSkill
- sc-readmeSkill
- sc-researchSkill
- sc-tddSkill
- sc-testSkill
- sc-workflowSkill
- sc-worktreeSkill
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
- Distinctive: line 61
Validate: check for existing files
- Distinctive: line 88
After running, you may need to:
- Very specific: line 89
Add ANTHROPIC_API_KEY secret for AI review
- Very specific: line 90
Run pre-commit install to enable hooks
- Very specific: line 91
Add PYPI_API_TOKEN / NPM_TOKEN / CARGO_REGISTRY_TOKEN for publishing
- Very specific: line 92
Add CODECOV_TOKEN for coverage reporting
≈ “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.
Files
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
| Flag | Description |
--lang | Force project language: python, node, go, rust |
--yes | Accept defaults, skip confirmation prompts |
--force | Overwrite existing workflow files (backs up originals) |
--minimal | Only essential CI workflow |
--full | All 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
- Detect project type from manifest files
- Configure based on flags (minimal/full/default)
- Validate check for existing files
- Present summary of what will be created
- Confirm (skip with
--yes) - Generate workflow files from templates
- 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 --forcePost-Setup
After running, you may need to:
- Add
ANTHROPIC_API_KEYsecret for AI review - Run
pre-commit installto enable hooks - Add
PYPI_API_TOKEN/NPM_TOKEN/CARGO_REGISTRY_TOKENfor publishing - Add
CODECOV_TOKENfor coverage reporting
Template Location
Templates are in templates/workflows/{python,node,go,rust}/:
ci.yml.j2- Main CI pipelinesecurity.yml.j2- Security scanningai-review.yml.j2- AI code reviewpublish.yml.j2- Package publishingpre-commit-config.yaml.j2- Pre-commit hooks
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
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.

