Ci

Route based on the argument:

setup (default if no argument)

Walk the user through full CI setup. Detect their CI platform and project type, then generate the appropriate config. Follow these steps:

1. Detect CI platform — look for .github/workflows/, .gitlab-ci.yml, Jenkinsfile, .circleci/, bitbucket-pipelines.yml, azure-pipelines.yml
2. Detect project type — check package.json, go.mod, pyproject.toml, Cargo.toml
3. Check if .qualitygate.yaml exists — if not, offer to create one
4. Generate CI config using the templates below
5. Generate helper scripts from ${CLAUDE_SKILL_DIR}/scripts/
6. Explain what each part does — don't just dump config

diagnose

Debug a failing CI quality gate run:

1. Ask for the CI log or read it from a provided URL/file
2. Check common issues (see Troubleshooting section)
3. Suggest fixes

pr-comment

Set up automatic PR comments with quality gate results:

1. Generate the markdown report step
2. Add the PR comment action (platform-specific)
3. Show how to customize the comment template

baseline

Set up baseline comparison so legacy debt doesn't block PRs:

1. Run initial crivo run --save to capture baseline
2. Configure CI to use --new-code for PRs
3. Set up the baseline update workflow on main branch merges

show-config

Show the current quality gate configuration and explain each field. Read .qualitygate.yaml and annotate it.

CI Platform Templates

GitHub Actions (Primary)

Generate this workflow at .github/workflows/quality-gate.yml: