CI Agent — the chain as a pipeline citizen — refactor-chain · ship/verify

Bundle: refactor-chain (self-diagnosing, self-healing fix-it pipeline). Phase: ship/verify — the readiness report runs on PRs and pushes · Prerequisite: the repo consumes the composite action (a workflow step uses it) · Next: humans read the report; the chain itself runs in chat, not CI. Adaptivity / conditional: conditional on CI — this skill only activates when refactor-chain is being wired into or debugged inside a CI pipeline. Report-only in every mode: the action never edits, pushes, or merges.

Purpose

In chat, the chain refactors. In CI, it only reports. The composite GitHub Action (action.yml at the plugin root) produces a refactor-readiness report for any repository — what lane it is, how confident the classification is, which guideline gaps exist and how severe — and publishes it where engineers already look: the job summary and, optionally, one calm PR comment. Two modes, one hard line: deterministic mode needs zero credentials; agent mode borrows the user's own agent CLI and key, and even then remains read-only. CI is the one place a wrong move is amplified by automation, so the guardrails here are the point.