Testing
Unit tests, integration tests, test automation
epidemiologist-analyst
by rysweet
Analyzes disease patterns and health events through epidemiological lens using surveillance systems, outbreak investigation methods, and disease modeling frameworks. Provides insights on disease spread, risk factors, prevention strategies, and public health interventions. Use when: Disease outbreaks, health policy evaluation, risk assessment, intervention planning. Evaluates: Transmission dynamics, risk factors, causality, population health impact, intervention effectiveness.
novelist-analyst
by rysweet
Analyzes events through narrative lens using story structure, character arc analysis, dramatic tension, thematic development, and narrative theory (three-act structure, hero's journey, conflict-resolution). Provides insights on narrative coherence, character motivations, dramatic stakes, plot development, and thematic resonance. Use when: Complex human stories, leadership analysis, organizational narratives, crisis narratives, cultural moments. Evaluates: Character development, narrative arc, dramatic tension, thematic depth, symbolic meaning, narrative coherence.
outside-in-testing
by rysweet
Generates agentic outside-in tests using gadugi-agentic-test framework for CLI, TUI, Web, and Electron apps. Use when you need behavior-driven tests that verify external interfaces without internal implementation knowledge. Creates YAML test scenarios that AI agents execute, observe, and validate against expected outcomes. Supports progressive complexity from simple smoke tests to advanced multi-step workflows.
challenge-that
by NTCoding
"Force critical evaluation of proposals, requirements, or decisions by analyzing from multiple adversarial perspectives. Triggers on: accepting a proposal without pushback, 'sounds good', 'let's go with', design decisions with unstated tradeoffs, unchallenged assumptions, premature consensus. Invoke with /challenge-that."
bun
by knoopx
Initializes projects, manages dependencies, runs scripts, executes tests, and bundles code using Bun. Use when working with package.json, installing packages, running dev servers, or building for production.
swe
by knoopx
Applies software engineering best practices, design principles, and avoids common anti-patterns. Use when designing systems, reviewing code quality, refactoring legacy code, making architectural decisions, or improving maintainability.
vitest
by knoopx
Writes and runs tests, configures test environments, mocks dependencies, and generates coverage reports. Use when setting up vitest.config.ts, writing test suites, mocking modules, or measuring code coverage.
newebpay
by paid-tw
Provides NewebPay integration overview and guides users to the appropriate skill. Use when starting NewebPay integration, setting up environment, or needing general guidance about 藍新金流.
file-organizer
by crazynomad
Mac 智能文件整理助手，专注整理下载文件夹中的办公文档，避免误移动代码文件
apple-swift
by maroffo
"Apple platform development with Swift 6, SwiftUI, async/await, and performance. Use when working with .swift files, Package.swift, Xcode projects, or building for iOS/macOS/watchOS/visionOS."
ruby
by maroffo
"Ruby gem development with modern tooling, testing, and publishing. Use when working with .gemspec, Rakefile, or user asks about gem structure, RSpec for gems, Bundler, or gem publishing. Not for Rails apps (use rails skill)."
superplan
by adamos486
Use when starting significant features, epics, or complex tasks. Creates multi-phase implementation plans with parallelizable phases, poker estimates, TDD-first acceptance criteria, and quality gates. Detects tech stack from CLAUDE.md/AGENTS.md (bypassing internet research if complete) or via codebase scan.
code-review-checklist
by ils15
Systematic code review using quality gates, SOLID principles, error handling patterns, and test coverage analysis. Provides structured feedback with severity levels and actionable improvements.
tdd-with-agents
by ils15
"Comprehensive TDD enforcement guide — RED→GREEN→REFACTOR cycle across backend, frontend, and database agents"
superval
by adamos486
Use when a plan has been built with superbuild or autobuild and you need to validate that every feature was implemented correctly, wired properly, and actually works end-to-end. Use after superbuild or autobuild completes, or when the user wants proof the build matches the plan.
playwright-e2e-testing
by ils15
Write end-to-end tests with Playwright for web applications. Includes fixtures, page objects, test templates, visual regression testing, and accessibility audits.
superbuild
by adamos486
Use when executing implementation plans phase-by-phase with strict enforcement of quality gates, tests, and Definition of Done. Triggers on "build this plan", "execute plan", "implement phases", or when user provides a plan document to execute.
artifact-management
by ils15
"Complete guide to the artifact trail system - plans directory structure, templates, and best practices for documenting feature implementations"
orchestration-workflow
by ils15
"Practical step-by-step walkthrough for orchestrating features end-to-end using the multi-agent system, from planning through deployment"
database-migration
by ils15
"Database migrations with Alembic - forward scripts, rollbacks, testing, zero-downtime deployment"
qa-expert
by zhaono1
Quality assurance expert for testing strategies and quality gates. Use when planning test coverage, setting up QA processes, or improving quality standards.
code-reviewer
by zhaono1
Reviews pull requests and code changes for quality, security, and best practices. Use when user asks for code review, PR review, or mentions reviewing changes.
forge-implement-issue
by mgratzer
Implement a feature or fix based on a GitHub issue, following project standards. Use when the user wants to start working on a GitHub issue, implement a feature, fix a bug, or begin coding from an issue number or URL.
fork-test
by Geeksfino
Minimal skill for testing context fork behavior. Do not use in production.