compose-preview-cilisted

# Compose Preview — CI setup Wiring the `compose-preview` CI surface into a repository: a `compose-preview/main` baselines branch, sticky before/after diff comments on pull requests, and the choices that decide whether one workflow is enough or you need two. This skill is about **standing the pipeline up and keeping it working**. For *reading* the diffs it produces — reviewing a UI PR, triaging a flaky preview — see the [**compose-preview-review**](../compose-preview-review/SKILL.md) skill. For driving the renderer by hand, see [**compose-preview**](../compose-preview/SKILL.md). ## Source Maintained at [github.com/yschimke/skills](https://github.com/yschimke/skills) under `skills/compose-preview-ci/`. The composite actions described here ship from [yschimke/compose-ai-tools](https://github.com/yschimke/compose-ai-tools); the canonical, always-current input reference is that repo's [`.github/actions/apply/README.md`](https://github.com/yschimke/compose-ai-tools/blob/main/.github/actions/apply/README.md). When this skill and that README disagree, the README wins — check it before telling a user an input doesn't exist. ## Decide the shape first Everything is one composite action, `apply`. What differs is how many jobs and workflows you wrap around it. | Situation | Shape | Read | |---|---|---| | PRs come from branches in the repo itself | **One job**, one workflow | [§ The single-job workflow](#the-single-job-workflow) | | PRs can come from **forks** (any public repo, OSS