output-error-try-catch
Fix try-catch anti-pattern in Output SDK workflows. Use when retries aren't working, errors are being swallowed, seeing unexpected FatalError wrapping, or when step failures don't trigger retry policies.
Fix try-catch anti-pattern in Output SDK workflows. Use when retries aren't working, errors are being swallowed, seeing unexpected FatalError wrapping, or when step failures don't trigger retry policies.
Workflow patterns from go-agents-orchestration library. Use when implementing workflows, state management, checkpoints, or parallel processing. Triggers: StateGraph, workflows.Register, WorkflowFactory, state.State, Observer, CheckpointStore, ProcessParallel, MultiObserver, StreamingObserver, graph.Execute, graph.Resume, OnEvent, workflow_runs, stages, decisions. File patterns: internal/workflows/*.go, workflows/**/*.go
Validate and register new Claude Code Skill manifests (.skill.yaml) to ensure structure, inputs/outputs, and dependencies are correct.
Multi-perspective quality review gate with architect, security, quality, tester, and performance stakeholders
Implement human-in-the-loop approval flows. Use when adding Slack approvals, dashboard review queues, action gating, or trust-based auto-approval.
Expert DevOps pour CI/CD, containers, Kubernetes et Infrastructure as Code. Utilise ce skill quand: (1) mise en place de pipelines CI/CD, (2) containerisation avec Docker/K8s, (3) infrastructure as code (Terraform, Pulumi), (4) monitoring et alerting, (5) optimisation des déploiements, (6) sécurisation de l'infrastructure.
Run and debug a repo verification pipeline (`./verify.sh --ui=false` or equivalent), including stage selection and opt-in E2E tiers.
azd up/azd provisionの影響分析、Bicep what-if実行とノイズフィルタリング。インフラ変更・デプロイ前の影響確認時に使用。
Level 3 patterns - test-smart, deploy, migrate, logs, status (production systems)
Document how to group Laravel seeders between local and shared environments, ensure seeders guard against duplication, and keep reruns safe.
Notice and address deprecation warnings immediately in test output, CI/CD logs, and development - read the warning, check migration guides, update code to use recommended APIs, don't suppress warnings. Use when seeing deprecation warnings, DeprecationWarning messages, or deprecated API notices.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches core:code-reviewer subagent to review implementation against plan or requirements before proceeding
Use when you have a spec or requirements for a multi-step task, before touching code
Agent-first workflow and design rails for building X07 programs with the released toolchain (no repo-only dependencies). Canonical execution is via `x07 run`.
Validate that the current VM has the right `agent-skills` installed for the repo you’re working in.
Implement liveness, readiness, and dependency health checks
Standard Go security toolkit: race detector, golangci-lint, Trivy, govulncheck. Zero cost, seamless integration, and OpenSSF-certified security workflow patterns.
This skill should be used when the user asks about build status in GCP, Google Cloud Build, or gcloud builds. Trigger phrases include "monitor the build", "watch the build", "check build status", "build in test environment", "build in staging", "build in production", "status of the build", "gcloud builds", "Cloud Build", "GCP build", "what happened with the build", "why did the build fail", "analyze the build failure", "did the build succeed", "check the deploy", "monitor the deploy", "anything weird with the build", or when user mentions checking CI/CD status in Google Cloud. Also use when user wants to use gcloud CLI to check build results or logs. Use proactively after merging a PR when build monitoring would be helpful.
Expert GitLab CI/CD engineer specializing in complex pipeline design, artifact management, and deployment strategies. Masters .gitlab-ci.yml configuration, runners, and GitOps practices for reliable software delivery.
Implement tasks from plans with test-first approach, user-story-centric execution, and AC verification. Use proactively when executing implementation plans. Enforces quality gates, MVP-first delivery, and Article VII story-by-story implementation.
Validate proposed stack against offline requirements. Use after initial stack proposal to identify gaps, assess complexity, and recommend adjustments.
Deploys WitchCityRope to staging environment on DigitalOcean. Automates build, registry push, server deployment, database migrations (if needed), health verification, and rollback capability. SINGLE SOURCE OF TRUTH for staging deployment automation.