- Home
- /
- Categories
- /
- Testing
Testing
Unit tests, integration tests, test automation
playwright-skill
by testdino-hq
Battle-tested Playwright patterns for E2E, API, component, visual, accessibility, and security testing. Covers locators, fixtures, POM, network mocking, auth flows, debugging, CI/CD (GitHub Actions, GitLab, CircleCI, Azure, Jenkins), framework recipes (React, Next.js, Vue, Angular), and migration guides from Cypress/Selenium. TypeScript and JavaScript.
java-development
by apache
Guides Java SDK development in Apache Beam, including building, testing, running examples, and understanding the project structure. Use when working with Java code in sdks/java/, runners/, or examples/java/.
WorldThreatModelHarness
by danielmiessler
Persistent world model system across 11 time horizons (6mo→50yr) for adversarial analysis of ideas, strategies, and investments. USE WHEN threat model, world model, test idea, test strategy, future analysis, test investment, how will this hold up, test against future, update world models, view world models, time horizon analysis, adversarial future test, stress test idea.
table-driven-test
by cockroachdb
Guidelines for creating clean, well-structured table-driven tests in Go following CockroachDB conventions.
testing-dbt-models
by AltimateAI
Adds schema tests and data quality validation to dbt models. Use when working with dbt tests for: (1) Adding or modifying tests in schema.yml files (2) Task mentions "test", "validate", "data quality", "unique", "not_null", or "accepted_values" (3) Ensuring data integrity - primary keys, foreign keys, relationships (4) Debugging test failures or understanding why dbt test failed Matches existing project test patterns and YAML style before adding new tests.
openspec-bulk-archive-change
by PBH-BTN
Archive multiple completed changes at once. Use when archiving several parallel changes.
openspec-sync-specs
by PBH-BTN
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-verify-change
by PBH-BTN
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
io-connectors
by apache
Guides development and usage of I/O connectors in Apache Beam. Use when working with I/O connectors, creating new connectors, or debugging data source/sink issues.
skill-finish-branch
by nyldn
Post-implementation: verify tests, merge/PR/keep/discard. Use when: AUTOMATICALLY ACTIVATE when user requests task completion with git operations:. "commit and push" or "git commit and push". "complete all tasks and commit and push"
atdd-team
by swingerman
This skill should be used when the user asks to "build a feature with a team", "use ATDD with agents", "create an ATDD team", "set up a team for ATDD", "orchestrate agents for ATDD", "use team-based development", "coordinate agents for feature development", "run the ATDD workflow with teammates", "add ATDD to my team", "extend my team with ATDD", "join the team with ATDD agents", "add spec-writer and reviewer to the team", or "add ATDD roles to the existing team". It orchestrates a three-agent team (spec-writer, implementer, reviewer) through a five-phase ATDD workflow: spec writing, spec review, pipeline generation, implementation, and post-implementation review. Supports extending an existing team with ATDD roles without replacing current teammates.
ticket-breakdown
by proflead
Break a task or ticket into small steps. Use when a junior developer needs guidance on how to start.
llm-patterns
by alinaqi
AI-first application patterns, LLM testing, prompt management
android-kotlin
by alinaqi
Android Kotlin development with Coroutines, Jetpack Compose, Hilt, and MockK testing
aws-sdk-java-v2-messaging
by giuseppe-trisciuoglio
Provides AWS messaging patterns using AWS SDK for Java 2.x for SQS queues and SNS topics. Handles sending/receiving messages, FIFO queues, DLQ, subscriptions, and pub/sub patterns. Use when implementing messaging with SQS or SNS.
Pentest Checklist
by zebbern
This skill should be used when the user asks to "plan a penetration test", "create a security assessment checklist", "prepare for penetration testing", "define pentest scope", "follow security testing best practices", or needs a structured methodology for penetration testing engagements.
skill-debate-integration
by nyldn
Internal: quality gates and export for AI debates. Use when: AUTOMATICALLY ACTIVATE when:. User runs /debate command. AI Debate Hub (.dependencies/claude-skills/skills/debate.md) is present
data-stats-analysis
by Starlitnightly
Perform statistical tests, hypothesis testing, correlation analysis, and multiple testing corrections using scipy and statsmodels. Works with ANY LLM provider (GPT, Gemini, Claude, etc.).
rails-query-object
by ThibautBaissac
Creates query objects for complex database queries following TDD. Use when encapsulating complex queries, aggregating statistics, building reports, or when user mentions queries, stats, dashboards, or data aggregation.
dust-llm
by dust-tt
Step-by-step guide for adding support for a new LLM in Dust. Use when adding a new model, or updating a previous one.
feature-dev
by sd0xdev
"Feature development workflow. Use when: implementing features, writing code, running dev loop. Not for: understanding code (use code-explore), reviewing code (use codex-code-review). Output: implemented feature + tests + review gate."
feasibility-study
by sd0xdev
"Feasibility analysis from first principles. Use when: evaluating solutions before tech-spec, comparing approaches, risk assessment. Not for: implementation (use feature-dev), architecture advice (use codex-architect). Output: quantitative comparison + recommendation."
tech-spec
by sd0xdev
"Tech spec generation and review. Use when: designing features, writing specs, requirement analysis. Not for: implementation (use feature-dev), architecture advice (use codex-architect). Output: numbered tech spec document."
playwright-e2e
by comet-ml
Playwright E2E test generation workflow for Opik. Use when generating, fixing, or planning automated tests in tests_end_to_end/.