GitHub
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
☆ 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
deploy
Enforces local testing before any deployment. MUST be used before running vercel, git push, or any deployment command. Prevents deploying untested code.
☆ 0View skill
GitHub
version-control
Manage chart and image versions. Use for version queries, bumping versions.
☆ 0View skill
GitHub
ralph-preflight
Pre-flight check for Ralph TUI loops. Validates config, templates, prd.json, and environment before starting a loop. Run after /prd to verify everything is ready. Detects global CLAUDE.md conflicts, validates t...
☆ 0View skill
GitHub
write-plan
Use when you have a spec or requirements for a multi-step task, before touching code
☆ 0View skill
GitHub
deployment-procedures
Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
☆ 0View skill
GitHub
phase-implementation-runbook
Enforce the Palette Kit v0.4 small-phase workflow. Use when working on any v0.4 phase implementation, validating docs/tests, packaging a patch, or preparing a commit/PR tied to the playbook.
☆ 0View skill
GitHub
multi-repo-dev-all
全リポジトリ並行実装スキル 複数リポジトリで並行してTDD実装を行い、依存関係を考慮した実行順序で実装します。
☆ 0View skill
GitHub
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code.
☆ 0View skill
GitHub
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before as...
☆ 0View skill
GitHub
setup
Initialize and set up local development environment with devflow infrastructure
☆ 0View skill
GitHub
cicd-debug-loop
Auto-debug this repo's dev→prod deployment pipeline with artifact promotion
☆ 0View skill
GitHub
ui-visual-audit
Advanced UI verification using Antigravity Manager's Vision MCP.
☆ 0View skill
GitHub
safety-protocol-enforcement
Absolute strict workflow rules to prevent unauthorized execution.
☆ 0View skill
GitHub
system-integration-validator
Validates system integration before deployment. Use when checking ports, database connections, frontend-backend APIs, or debugging blocked/stuck workflows. Detects dead ends, bottlenecks, circular dependencies.
☆ 0View skill
GitHub
deployment-safety
Enforces safe production deployment and rollback rules for a FinTech system.
☆ 0View skill
GitHub
managing-environment
Infrastructure Architect acting as the guardian of reproducibility. Manages package installations, environment setup, and containerization decisions with a "Docker First" mentality.
☆ 0View skill
GitHub
deployment-verification
Ensures changes are pushed to remote to trigger auto-deployment (Vercel/Netlify) and informs the user about the process.
☆ 0View skill
GitHub
verifying-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before as...
☆ 0View skill
GitHub
pr-checks
Wait for CI checks to pass, address automated feedback from Copilot, and mark PR ready for human review
☆ 0View skill
GitHub
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
☆ 0View skill
GitHub
parallel-agents-orchestration
Dispatch concurrent agent workflows for independent problems
☆ 0View skill
GitHub
vercel-deployment-cdn
Deploy frontend, manage CDN caching, and automate deployments via Vercel MCP
☆ 0View skill
GitHub
www-studio
Use this skill when building websites, landing pages, or UI components using reference bank patterns. Triggers include "build a site like X", "create landing page", "implement this design", or when referencing...
☆ 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.