GitHub
execution-engine
Core execution workflow - Plan, Execute, Verify, Commit cycle for autonomous development
☆ 0View skill
tools cicd AI Skills
Discover tools cicd skills, compare source repositories and read the instructions for each workflow.
Categories: tools cicd
tools cicd Clear filters
Browse skills
GitHub
architecture-review-and-approval
Run structured architecture reviews with stakeholders and sign-off.
☆ 0View skill
GitHub
project-context
OpenCivilizations project architecture, patterns, and conventions. Auto-applies for implementation tasks to ensure consistency.
☆ 0View skill
GitHub
threat-modeling-framework
Perform STRIDE analysis and mitigation planning.
☆ 0View skill
GitHub
feature-dev
Complete feature development workflow from spec to delivery with review and testing
☆ 0View skill
GitHub
repository-organization
Guidelines for establishing and maintaining a standardized, intuitive, and automated repository environment to minimize technical debt and ensure long-term maintainability.
☆ 0View skill
GitHub
java-contract-testing
Establish contract testing (OpenAPI + consumer-driven contracts) with compatibility gates to prevent breaking changes in microservices. Use when API evolution risks breaking consumers or when you need CI enforc...
☆ 0View skill
GitHub
bacchus
Multi-agent coordination for parallel development. Use when asked to parallelize work, coordinate multiple agents, or manage tasks across a codebase.
☆ 0View skill
GitHub
project-manager
Orchestrate multi-agent development workflows. Use when starting a new feature to coordinate architecture design, implementation, code review, and release through specialized sub-agents.
☆ 0View skill
GitHub
docker-kubernetes
Containerization, orchestration, and deployment with Docker and K8s
☆ 0View skill
GitHub
long-term-debt-tracker
Tracks, classifies, and prioritizes technical debt (code, spec, and process) over time. Use to prevent silent rot.
☆ 0View skill
GitHub
playwright
Playwright E2E testing patterns and best practices. Trigger: When writing or running E2E tests.
☆ 0View skill
GitHub
nestjs-testing
Unit and E2E testing strategies with Docker.
☆ 0View skill
GitHub
docker-guide
Best practices for Dockerizing Remix/Shopify apps. Includes multi-stage builds, Alpine images, and local dev setups with pnpm.
☆ 0View skill
GitHub
rapid-prototyper
Rapid Prototyper balancing speed with "upgrade paths" to ship clear, working end-to-end demos quickly.
☆ 0View skill
GitHub
deployment-devops
Deploy to production with Vercel and manage environment
☆ 0View skill
GitHub
releasing-version
Updates documentation, generates changelogs, and handles versioning. To be used for automating release tasks.
☆ 0View skill
GitHub
qa-tester
Activates when user requests test strategy design, automated testing frameworks, test case design, load testing, or security testing. Do NOT use for fixing bugs in production code. Examples: 'Write PHPUnit test...
☆ 0View skill
GitHub
risk-and-assumption-tracker
Capture risks, assumptions, and mitigation plans throughout delivery.
☆ 0View skill
GitHub
release-management
Manage releases, deployments, and rollback strategy with clear versioning and environment policy. Use when planning or executing a release, or setting deployment workflow.
☆ 0View skill
GitHub
docker-dev-env
Create Docker-based development environments with docker-compose. Use when users want to set up containerized dev environments, create Dockerfile/docker-compose.yml for projects, or need isolated development co...
☆ 0View skill
GitHub
ci-cd-pipeline-orchestrator
Build pipelines with blue-green, canary, and feature flags.
☆ 0View skill
GitHub
feature-creator
Guide for creating DevContainer features. Use when creating a new feature for devcontainer, implementing install.sh scripts (npm package, binary download, source build, dotnet tool, or directory setup patterns)...
☆ 0View skill
GitHub
rolling-update-strategies
Zero-downtime deploys with health checks and rollback.
☆ 0View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.