testing
0
test-driven-development
機能実装やバグ修正時に使用。RED-GREEN-REFACTORサイクルとTesting Trophy手法を強制。
TakumiOkayasu
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
testing
0
automated-testing
Write automated tests following a pragmatic, integration-focused philosophy. Use when writing tests for new features, writing tests for bug fixes, adding test coverage, or deciding what/how to test. Emphasizes confidence over coverage, real objects over mocks, integration over isolation, and simplicity over dogma.
conradbeach
testing-security
testing
0
rspec-core
This skill should be used when the user asks to "write an RSpec test", "create a spec", "use describe blocks", "set up let variables", "use before hooks", "understand RSpec structure", mentions "subject", "context", "it blocks", or needs guidance on RSpec 3.x fundamentals and test structure.
bastos
testing-security
testing
0
write-scenario
Write BDD scenarios in Gherkin format (Given/When/Then) in pure business language. Use when creating acceptance tests, user story scenarios, or stakeholder-readable specifications.
foolishimp
testing-security
testing
0
playwright-testing
Use when writing, debugging, or reviewing Playwright tests for web apps; before writing test code; when tests are flaky, slow, or brittle; when seeing timeout errors, element not found, or race conditions; when using getByRole, locators, or assertions
mhagrelius
testing-security
testing
0
openspec-check
Use BEFORE any implementation to check if specs exist for the capability. Run this first when starting any feature work. Reports: spec exists, no spec, or active change in progress.
discountedcookie
testing-security
testing
0
testing-patterns
Express testing patterns including unit tests, integration tests, API endpoint testing, mocking databases, testing middleware, testing authentication. Use when writing tests for Express APIs, testing controllers and services, mocking dependencies, or testing middleware.
karchtho
testing-security
testing
0
testing-patterns
Table-driven tests, mocking strategies, and comprehensive testing patterns. Use when writing tests.
IvanTorresEdge
testing-security
testing
0
test-driven-development
Write failing test first, then minimal code to pass (RED-GREEN-REFACTOR cycle). WHEN: MUST use when implementing new features, fixing bugs, refactoring. Invoke with "/test-driven-development" or "use TDD". Always write test BEFORE implementation code. WHEN NOT: Throwaway prototypes, generated code, configuration files, debugging root cause (use systematic-debugging first).
LounisBou
testing-security
testing
0
testing-patterns
REST integration testing patterns with JUnit 5, Mockito, RestAssured. Use when writing integration tests that mock external dependencies, use Testcontainers/H2 for databases, and test endpoints with raw JSON bodies.
emvnuel
testing-security
testing
0
writing-good-tests
Use when writing or reviewing tests - covers test philosophy, condition-based waiting, mocking strategy, and test isolation
pbdeuchler
testing-security
testing
0
blueprint-develop
Use for test-driven development of trading strategies. Supports Ralph Loop iterative mode for complex implementations. Ensures backtest interface alignment, atomic implementation, synchronized test updates, PM regression prevention, and dependency impact analysis.
morris-y
testing-security
testing
0
ruby-testing
Ruby/RSpec testing guidelines and workflow following project conventions. Use when writing or improving Ruby tests.
arowinski
testing-security
testing
0
eval
Generate evaluation specs with building and verification criteria. Use when setting up features, defining acceptance criteria, or before implementing anything significant. Triggers on "create evals", "set up verification", "define acceptance criteria", or "build [feature]".
harivansh-afk
testing-security
testing
0
bug-reproduction-test-generator
Generates failing tests that reproduce reported bugs in FanHub. Use when a bug report comes in and you need to create a test that demonstrates the issue before fixing it. Follows FanHub's testing patterns and data integrity rules.
MSBart2
testing-security
testing
0
oe-security-prompt-injection
Maintain and extend prompt-injection defenses. Use when adding new user-input surfaces, changing prompt templates, or when a new injection pattern is observed; run the security regression suite and add a minimal new test case.
shami-ah
testing-security
testing
0
tdd-refactor
テストを維持しながらコード品質を改善する。GREENの次フェーズ。「リファクタして」「refactor」で起動。
morodomi
testing-security
testing
0
testing-test-writing
Write strategic tests following best practices including minimal tests during development, focus on core user flows only, defer edge case testing until later, test behavior not implementation, use clear descriptive test names, mock external dependencies, and maintain fast execution times. Use this skill when deciding which tests to write during feature development, determining appropriate test coverage levels, writing tests for critical user flows, choosing between unit and integration tests, implementing test mocking strategies, or balancing test coverage with development velocity. This skill applies when working on test files and determining testing strategy for features.
FlorianRiquelme
testing-security
testing
0
test-driven-development
Use when implementing any feature, bugfix, or code change. Invoke BEFORE writing implementation code. The Iron Law - no production code without a failing test first.
erikpr1994
testing-security
testing
0
testing-e2e-with-playwright
Run end-to-end browser tests using Playwright MCP. Use when testing web applications, validating user journeys, checking UI interactions, or when the user mentions E2E tests, browser automation, or Playwright.
amo-tech-ai
testing-security