cicdlisted

# cicd CI/CD patterns and the why behind them. Flex them to fit the app and the user's requests. - The principles are platform-agnostic; **GitHub Actions is the reference implementation** - Check `references/`](references/) recipes and [`assets/`](assets/.github/workflows/) workflows are GHA, the philosophy holds on any CI system. - This skill uses `mise` as the task runner; substitute the project's own (e.g. Make) the patterns hold tho. # How to use the Skill The skill uses progressive disclosure: each area routes to a `references/` file holding the actual rules and recipes. Read the matching one **before** planning or building that pipeline, not after. SKILL.md alone is not enough. Plan ahead, and read all references you'll need! ## When to read references Always read at-least 1 reference from the router below. Depending on your goal you might want to read more than 1 reference. Be eager to load local .md references. Do not load online links/references unless you really need to, default to trust your knowledge. Only load online reference when you need to learn more. ## Router **CI checks** (lint / test / validation workflows) -> [`references/checks.md`](references/checks.md) CI Tasks best practices. **Releases** (versioning, tagging, notes, RCs) -> [`references/releases.md`](references/releases.md) Label-driven bump, auto-tag on merge, the gate + preview comment, generated notes and label taxonomy, release candidates, the release-drafter draft variant. **Publish