GitHub
release
This skill should be used when the user asks to "make a release", "create release", "release leihs", or "/release". Automates Leihs RC.1, RC.2, and stable release workflows following the zhdk-intern process wit...
Skills IA blockchain cicd
Découvrez les skills blockchain cicd, comparez leurs dépôts et consultez leurs instructions.
Catégories: blockchain cicd
blockchain cicd Effacer les filtres
Explorer
GitHub
quality-enforcer
Enforces quality gates: 80% test coverage, passing tests, successful builds, semantic versioning. Runs before PR creation. Use when: Running tests, checking coverage, validating quality, versioning Triggers:...
GitHub
viya-dev-environment
Manage viya-app local development environment. Use when setting up services from PRs, troubleshooting container issues, restarting Docker services, switching service versions, or debugging local dev environment...
GitHub
ci-workflow
Generate GitHub Actions workflows that use devflow CLI for migrations, deployments, and validation
GitHub
implement
Execute approved plan incrementally with verification at each step. Use after plan is approved.
GitHub
check-secure-files
Enforces a checklist to verify that all required secure configuration files (google-services.json, GoogleService-Info.plist, environment-configs.json) are present for all environments (dev, stg, prd).
GitHub
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
GitHub
deploy
Enforces local testing before any deployment. MUST be used before running vercel, git push, or any deployment command. Prevents deploying untested code.
GitHub
version-control
Manage chart and image versions. Use for version queries, bumping versions.
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...
GitHub
write-plan
Use when you have a spec or requirements for a multi-step task, before touching code
GitHub
deployment-procedures
Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
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.
GitHub
multi-repo-dev-all
全リポジトリ並行実装スキル 複数リポジトリで並行してTDD実装を行い、依存関係を考慮した実行順序で実装します。
GitHub
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code.
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...
GitHub
dotnet
Work on the .NET solution for ApiOrchestratorSphere. Use this when editing services, components, JSON data, or tests.
GitHub
setup
Initialize and set up local development environment with devflow infrastructure
GitHub
cicd-debug-loop
Auto-debug this repo's dev→prod deployment pipeline with artifact promotion
GitHub
ui-visual-audit
Advanced UI verification using Antigravity Manager's Vision MCP.
GitHub
safety-protocol-enforcement
Absolute strict workflow rules to prevent unauthorized execution.
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.
GitHub
deployment-safety
Enforces safe production deployment and rollback rules for a FinTech system.
GitHub
managing-environment
Infrastructure Architect acting as the guardian of reproducibility. Manages package installations, environment setup, and containerization decisions with a "Docker First" mentality.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.