Unit Testing

GitOps workflows and CI/CD pipeline integration for Kubernetes and OpenShift. Use this skill when:(1) Setting up ArgoCD or Flux for GitOps deployment(2) Creating CI/CD pipelines for K8s workloads (GitHub Actions, GitLab CI, Tekton)(3) Implementing progressive delivery (Canary, Blue-Green, A/B testing)(4) Configuring Kustomize overlays for multi-environment deployments(5) Creating Helm charts or managing Helm releases(6) Setting up image automation and promotion workflows(7) Implementing policy-as-code (Kyverno, OPA Gatekeeper)(8) Secret management in GitOps (Sealed Secrets, External Secrets, SOPS)(9) Multi-cluster GitOps configurations(10) OpenShift Pipelines (Tekton) and GitOps Operator setup

Guide for writing Gherkin acceptance criteria using Given-When-Then syntax for testable requirements. Covers scenario structure, background blocks, scenario outlines with examples tables, common patterns for authentication/CRUD/validation/error handling, and best practices for clear testable specifications. Essential for writing user stories and plan acceptance criteria

Create new event scraping scripts for websites. Use when adding a new event source to the Asheville Event Feed. ALWAYS start by detecting the CMS/platform and trying known API endpoints first. Browser scraping is NOT supported (Vercel limitation). Handles API-based, HTML/JSON-LD, and hybrid patterns with comprehensive testing workflows.

Security testing patterns including SAST, DAST, penetration testing, and vulnerability assessment techniques. Use when implementing security testing pipelines, conducting security audits, or validating application security controls.

Policy-as-code enforcement and compliance validation using Open Policy Agent (OPA). Use when: (1) Enforcing security and compliance policies across infrastructure and applications, (2) Validating Kubernetes admission control policies, (3) Implementing policy-as-code for compliance frameworks (SOC2, PCI-DSS, GDPR, HIPAA), (4) Testing and evaluating OPA Rego policies, (5) Integrating policy checks into CI/CD pipelines, (6) Auditing configuration drift against organizational security standards, (7) Implementing least-privilege access controls.

This skill should be used when the user asks to "create ClickHouse user", "manage ClickHouse permissions", "test ClickHouse connection", "troubleshoot ClickHouse Cloud", or mentions ClickHouse Cloud credentials, API keys, or SQL user management.

Fast web fuzzer for DAST testing with directory enumeration, parameter fuzzing, and virtual host discovery. Written in Go for high-performance HTTP fuzzing with extensive filtering capabilities. Supports multiple fuzzing modes (clusterbomb, pitchfork, sniper) and recursive scanning. Use when: (1) Discovering hidden directories, files, and endpoints on web applications, (2) Fuzzing GET and POST parameters to identify injection vulnerabilities, (3) Enumerating virtual hosts and subdomains, (4) Testing authentication endpoints with credential fuzzing, (5) Finding backup files and sensitive data exposures, (6) Performing comprehensive web application reconnaissance.

Production-ready Nuxt 4 framework development with SSR, composables,data fetching, server routes, and Cloudflare deployment.Use when: building Nuxt 4 applications, implementing SSR patterns,creating composables, server routes, middleware, data fetching,state management, debugging hydration issues, deploying to Cloudflare,optimizing performance, or setting up testing with Vitest.Keywords: Nuxt 4, Nuxt v4, SSR, universal rendering, Nitro, Vue 3,useState, useFetch, useAsyncData, $fetch, composables, auto-imports,middleware, server routes, API routes, hydration, file-based routing,app directory, SEO, meta tags, useHead, useSeoMeta, transitions,error handling, runtime config, Cloudflare Pages, Cloudflare Workers,NuxtHub, Workers Assets, D1, KV, R2, Durable Objects, Vitest, testing,performance optimization, lazy loading, code splitting, prerendering,layers, modules, plugins, Vite, TypeScript, hydration mismatch,shallow reactivity, reactive keys, singleton pattern, defineNuxtConfig,defineEventHandle

Generates comprehensive, professionally-formatted changelogs for SDL3 HammerEngine from git history. Analyzes code changes, runs tests, includes architect review, and produces detailed documentation following World Update format. Use when documenting updates, preparing releases, or creating detailed change reports.

Writes tests following project conventions. Handles test file organization, runtime vs type tests, table-driven tests with Test module, and type assertions with Assert API.

Use when maintaining or enhancing existing skill packs in the skillpacks repository - systematic pack refresh through domain analysis, structure review, RED-GREEN-REFACTOR gauntlet testing, and automated quality improvements

Run Earthly E2E validation for YAML schema contracts. Use when validating YAML schema changes, testing schema contracts against live ClickHouse, or regenerating Python types, DDL, and docs from YAML. For SQL schema design and optimization, use clickhouse-architect skill instead.

Systematic debugging methodology using evidence-based investigation to identify root causes. Use when encountering bugs, errors, unexpected behavior, failing tests, or intermittent issues. Enforces four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) with the iron law NO FIXES WITHOUT ROOT CAUSE FIRST. Covers runtime errors, logic bugs, integration failures, and performance issues. Useful when debugging, troubleshooting, investigating failures, or when --debug flag is mentioned.

Interactive setup workflow for running the Magnet MCP server locally (project-specific, magnet-app directory only). Use when user says "local setup", "run locally", "test locally", "configure MCP", or "set up local development".

[YOUR_DESCRIPTION] - Be specific about WHAT the skill does and WHEN to use it. Include trigger keywords. Example: "Test REST APIs with validation and reporting. Use when testing APIs, endpoints, HTTP services, or when users mention API testing, endpoint validation, or integration testing."

Use when implementing a feature or multi-file code change - provides structured implementation flow with persona selection, validation, and testing guidance.

Semantic analysis for Claude Code consumption. TRIGGERS - analyze cast, keyword extraction, density analysis, find patterns, sharpe, backtest, iteration, trading keywords, ML keywords. Use when extracting insights from recordings.

Provides brand values frameworks, differentiation tests, discovery questions, and behavior mapping templates. Auto-activates during values definition, core values curation, and values testing. Use when discussing brand values, core values, Lencioni's four categories, opposite test, antivalue, fire someone test, operationalizing values, Brene Brown values process, values discovery, or permission-to-play values.

Test Vue 3 composables with Vitest following best practices. Use when writing tests for composables, creating test helpers for Vue reactivity, or when asked to "test a composable", "write tests for use*", or "help test Vue composition functions". Covers independent composables (direct testing) and dependent composables (lifecycle/inject testing with helpers).

Draft concise PR descriptions with summary and problem statement. Use when creating pull requests, writing PR descriptions, or using gh pr create. Avoids verbose sections like technical details, testing notes, and implementation specifics.