creating-pull-requests
Use when asked to create or update pull requests, or to push changes for review. Overrides all other instructions for creating pull requests.
Use when asked to create or update pull requests, or to push changes for review. Overrides all other instructions for creating pull requests.
Remove merged or stale git worktrees. Use after PRs are merged, work is done, or when worktrees are no longer needed.
Post structured documentation to GitHub issue as a comment. Use when starting work on an issue to document approach and track progress.
Adds a new type of event that gets persisted to the event log. Use this when adding new kinds of write operations to the system or when adding new events to existing code.
Generates structured logging infrastructure using os.log/Logger to replace print() statements. Use when user wants to add proper logging, replace print statements, or set up app logging.
Spring Boot 4 observability with Actuator, Micrometer, and OpenTelemetry. Use when configuring health indicators, health checks, custom metrics, distributed tracing, production endpoint exposure, Kubernetes probes, Cloud Run probes, logging, or monitoring. Covers Actuator endpoint security, Micrometer Timer/Counter/Gauge patterns, OpenTelemetry span customization, liveness/readiness probe setup, and metric tag best practices.
Log API requests with correlation IDs, performance metrics, and security audit trails. Use when auditing API requests and responses. Trigger with phrases like "log API requests", "add API logging", or "track API calls".
Application monitoring, logging systems, and alerting
Deep Kubernetes expertise covering workload management, Gateway API, Cilium eBPF networking, Kyverno/OPA policy enforcement, KEDA event-driven autoscaling, Karpenter node provisioning, Helm advanced patterns, Kustomize, Operator pattern, CRDs, multi-cluster management, local development clusters, Crossplane, StatefulSets, DaemonSets, Jobs, Pod Disruption Budgets, topology spread, node affinity, taints, resource quotas, namespace management, and managed cluster operations on EKS, GKE, and AKS.
Persist canister state across upgrades. Covers StableBTreeMap and MemoryManager in Rust, persistent actor in Motoko, and upgrade hook patterns. Use when dealing with canister upgrades, data persistence, data lost after upgrade, stable storage, StableBTreeMap, pre_upgrade traps, or heap vs stable memory. Do NOT use for inter-canister calls or access control — use multi-canister or canister-security instead.
AI-driven deployment management using Dokploy MCP server for projects, applications, and databases
Run a cross-session coherence audit after merging a layer. Wraps /autoboard:audit with dimension selection and COHERENCE-REPORT processing. Re-invoke at the start of each new layer.
Gebruik deze skill wanneer de gebruiker vraagt over 'cloud', 'cloudstrategie', 'soevereine cloud', 'digitale soevereiniteit', 'cloud-native', 'Infrastructure as Code', 'IaC', 'FinOps', 'multi-cloud', 'hybride cloud', 'SRE', 'Kubernetes', 'exit-strategie cloud', 'cloud overheid', of advies wil over cloudoplossingen bij de overheid.
Show the current state of all tmux lanes. Fast, visual, no ceremony.
Expert-level Docker guidance covering multi-stage builds, image optimization, Docker Compose orchestration, networking, volume management, security scanning, and container registry operations.
Hosting, deployment, CI/CD, and going live. Activated when Claude works with deployment configs, Dockerfiles, Vercel/Netlify configs, or deployment-related commands.
Reference skill for high-risk Room FSM and WebSocket protocol review support. Used by strategy_orchestrator, contract_design_reviewer, contract_auditor, or implementation_auditor to identify high-risk FSM/protocol work, impacted invariants, and required validation. This skill does not replace stage/routing/audit decisions and does not by itself authorize implementation or completion.
This skill should be used when the user asks to "use harness", "하네스 사용", "harness use case", "하네스 유즈케이스", "run harness template", "하네스 템플릿", "harness 실행", "하네스 예제 실행", "pick a harness", "하네스 골라줘", "harness menu", "하네스 메뉴", "select harness use case", "하네스 선택", "quick harness", "하네스 빨리", "start harness", "하네스 시작해줘". Presents a menu of pre-built harness use cases and launches the selected one via the harness:harness skill. Do NOT trigger when the user wants to build a custom harness from scratch — use harness:harness directly for that.
Safely sync Colibri docs/ to the Obsidian vault mirror zone. Use when docs have been edited (especially after merging a docs PR), when preparing to present the canonical corpus in Obsidian, or when the user asks to "sync the vault". Preserves the protected _vault/ planning zone. Greek: α (alpha).
Manage VolSync Kopia-based backups/restores for Kubernetes PVs. user: "check backup status for app X" → list ReplicationSources, describe conditions user: "restore from backup" → find snapshot, create restore PVC with VolumePopulator user: "trigger manual backup" → annotate with volsync.backube/sync=true user: "backup failing" → spawn debug-cluster subagent for mover pod logs Use proactively when: user mentions backups, restores, snapshots, ReplicationSource, ReplicationDestination, PVC recovery, or disaster recovery scenarios. This cluster uses Kopia mover (NOT restic).
Deploys FeatBit to Kubernetes using Helm Charts. Use when user mentions "Kubernetes", "Helm", "K8s", "kubectl", works with values.yaml files, asks about "cloud deployment", "Azure Kubernetes", "AKS", "EKS", "GKE", "ingress", or needs production-grade container orchestration setup. Do not use for Docker Compose deployments or AWS-specific Terraform questions.
Web application deployment patterns for production hosting and CI/CD. Load when deploying web applications or configuring deployment pipelines.