Setup CI Automation

I work with a project's CI: find out what runs there today, explain it, and add new workflows that automate QA tasks on repository events. What a new workflow does comes from the skill that owns the task — this skill owns getting it into CI correctly.

Critical Constraints

• Only touch CI config files — never source or test files.
• Never invent the commands a job runs — take the payload from the skill that owns the task, or from the user.
• The finished result is CI configuration delivered through a PR — never pushed straight to the default branch.
• Secrets live in the CI's secret store, never in config files.

Workflow

Step 1 — Investigate the CI

• Read the repo's CI config files to identify the CI system; several or none → ask which one to target.
• Inventory the existing workflows: trigger, jobs, and purpose of each — new automation must fit in, not duplicate or break what's there.
• Note the primitives this CI offers: secret store, value passing between jobs and pipelines, cross-pipeline triggers, deploy events.