CI/CD pipeline
Build, test, security scan, deploy stages with immutable artifacts; fail fast and parallelize where safe.
Category · CI/CD & quality gates
CI/CD & quality gates
5 skills Category 14 of 20
This category automates quality signals before and after merge: pipeline stages, GitHub Actions reuse and secrets, CPU/memory profiling and flame graphs, frontend bundle budgets, and static-site SEO metadata. Layer with testing and static analysis for a full gate matrix.
In the hub it opens the “continuous delivery & infrastructure” band. The five entries match the main hub.
Quick links
In depth
GitHub Actions
Reusable workflows, matrices, environments, OIDC for secrets—pin third-party actions and use least-privilege tokens.
Performance profiling
CPU sampling, allocation profiling, async wait visualization—map hotspots to business code before micro-optimizing.
Frontend bundle size
Route-level code splitting, dependency swaps, tree-shaking audits—CI budgets with regression diffs.
SEO & metadata
title/description/canonical, Open Graph, structured data—consistent with static export or SSR rendering.