ci-cd-and-automation
Design CI/CD pipelines, quality gates, and iterate on failing PR checks until green. Use when setting up pipelines or fixing CI on a branch.
What this skill does
# 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. **Feature flags:** incomplete features, gradual rollout, kill switches, environment-specific behavior. **Quality gate order (fastest-failing first):** lint → typecheck → unit tests → build → integration → security → staging deploy → smoke → production. ## Pipeline design process 1. List required checks and order fastest-failing-first with clear pass/fail criteria. 2. Keep lint/typecheck under ~30s and unit tests under ~2 minutes where possible. 3. Automate staging on merge; production with approval or policy. 4. Track success rate and mean time to recovery; alert on blocked merges. ## CI failure iteration Use when checks are pending, failing, or you need to drive a branch to green. ```bash gh pr view --json number,url,headRefName gh pr checks --json name,bucket,state,workflow,link gh pr checks --watch --fail-fast # when pending gh run view <run-id> --log-failed # when GHA job failed ``` **Workflow:** 1. Resolve the active PR and inspect the full check set. 2. If already failed, diagnose the first actionable error (logs or check link). 3. If pending, watch with fail-fast. 4. Apply the smallest safe fix for one failure at a time. 5. Push, re-run `gh pr checks`, repeat until green. **Guardrails:** - One failure cause per fix when possible; no `--no-verify`. - If failure is unrelated and fixed on main, merge main instead of bloating the PR. - Retry flaky checks once and record flake evidence. - Re-check after every push—the check set can change. **Output:** current status, root error, fixes applied in order, PR URL when green. ## Anti-Rationalization | Excuse | Counter | |--------|---------| | "The pipeline can be fixed later" | Broken pipelines get bypassed. | | "Full automation is too much work" | Manual deploy is slower and error-prone. | | "Feature flags add complexity" | They prevent uncontrolled release risk. | | "We don't need staging" | Staging catches environment-specific failures. | | "The pipeline is fast enough" | Slow feedback discourages small commits. | ## Verification - [ ] Pipeline runs on every push and PR - [ ] Fastest checks run first - [ ] Deploy and rollback paths are automated and tested - [ ] CI iteration uses `gh pr checks` as authority
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.