cilisted

# /craftsman:ci - CI/CD Integration ## Outcome Contract - **Outcome**: a CI pipeline that enforces the same rules as the local hooks, from the same validators, the same rules engine and the same per-file severity resolution. - **Done when**: the generated pipeline file exists for the target provider, references the same pack validators as the hooks, and a dry run reports the same violations locally and in CI. - **Evidence**: craftsman-ci.sh output, the generated template, and the provider adapter used. Integrate Craftsman quality gates into your CI/CD pipeline. ## Subcommands - `/craftsman:ci export` - Generate `.github/workflows/craftsman-quality-gate.yml` - `/craftsman:ci status` - Show current CI integration status --- ## Execution ### If the user runs `/craftsman:ci export`: 1. Read `.craft-config.yml` if it exists to pick up `strictness` and `stack` settings. 2. Check for `composer.json` (PHP), `package.json` (Node.js), and `deptrac.yaml` to tailor the workflow. 3. Copy `ci/templates/craftsman-quality-gate.yml` into `.github/workflows/craftsman-quality-gate.yml`. - If `.github/workflows/` does not exist, create it. - If the file already exists, ask the user before overwriting. 4. Confirm the export with a summary: ``` Craftsman CI workflow exported to: .github/workflows/craftsman-quality-gate.yml Detected stack: <stack> Config: <strictness> strictness Next steps: 1. Commit and push: git add .github/workflows/craftsman-quality-gate.yml 2. Open a PR