Default output: return only the result, blockers, and required evidence. Omit preambles, process narration, repeated context, confidence scores, and follow-up offers. Use at most five bullets unless a required artifact or schema needs more.

CI/CD and Automation

Overview

Pipelines enforce quality automatically: catch issues early (shift left), ship in small batches, and use feature flags for safe release. When CI fails on a branch, iterate with gh pr checks as the source of truth—not GitHub Actions list alone.

When to Use

• Designing or changing build/deploy pipelines
• Adding quality gates or automated checks
• Watching or fixing CI on the current branch or PR

Core principles

Shift left: lint/format pre-commit, typecheck before push, unit tests on push, integration tests on PR, security scans on main.

Faster is safer: automate deploys, make rollbacks trivial, auto-deploy staging on merge.