agentuity-cli-repl
interactive REPL for testing
Discover testing security testing skills, compare source repositories and read the instructions for each workflow.
interactive REPL for testing
테스트, 테스팅, QA, 테스트 전략, 품질 보증 - Use when designing test strategies, writing test plans, or ensuring quality assurance. Guides systematic testing approach from unit to E2E with proper coverage and s...
Implements Z-Wave CTT (Certification Test Tool) test handlers for automating certification tests. Use when asked to create handlers for a given test, which includes automating CTT log parsing and prompt respons...
Test infrastructure patterns - PGlite for in-memory PostgreSQL, Redis/S3 mocks, TestSetup factory, Vitest. Use when writing tests or adding test infrastructure.
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof aga...
Validates discovered bugs with reproducing tests and validates fixes with regression tests. Called by other skills when bugs are found during optimization hunting. Creates unit tests and fuzz tests to prove bug...
Create and maintain runnable examples under examples/ for onboarding and smoke testing. Use when adding/changing public APIs, when you need a quick “does it work end-to-end?” script, or when updating examples/R...
テストコード作成と品質保証の規約
Comprehensive guide for Test-Driven Development (TDD) methodology. Use this skill when the user asks to implement features using TDD, write tests first, follow red-green-refactor cycle, or develop code with tes...
t.wada流TDD(テスト駆動開発)。新機能実装、バグ修正、リファクタリング時に自動適用。Red-Green-Refactorサイクル、AAA構造、振る舞いテストの原則に従う。テストを書く、テストファーストで実装する、テストコードをレビュ...
Strategy and patterns for designing and implementing End-to-End scenario tests using the Python SDK. Focuses on full-stack verification and SDK usability.
This skill should be used when the user asks about "spec methodology", "specification workflow", "spec-driven development", "how to write specs", "spec best practices", "specification templates", or needs guida...
This skill should be used when the user asks about "Rails testing", "RSpec", "Minitest", "request specs", "system specs", "FactoryBot", "fixtures", "test coverage", "testing controllers", "testing models", "int...
Implementation Agent: Full TDD workflow in a single context window. Writes tests, implements code, and iterates until all tests pass.
Reproduce bugs and gather evidence for root cause analysis. Use when investigating a bug report to confirm reproduction and collect detailed information about the failure.
Analyzes code diffs to identify affected endpoints and prioritize regression testing. Focuses QA effort on changed areas.
Implementation Agent: Full TDD workflow in a single context window. Writes tests, implements code, and iterates until all tests pass.
Analyze test failures and suggest fixes for Feature Swarm verification. Use when tests fail during the verification phase to diagnose root cause and determine if automatic recovery is possible.
Executes behavioral API tests by spinning up the service and making real HTTP requests. Validates status codes, response structure, and data correctness.
Implementation Agent: Full TDD workflow in a single context window. Writes tests, implements code, and iterates until all tests pass.
Analyze test failures and suggest fixes for Feature Swarm verification. Use when tests fail during the verification phase to diagnose root cause and determine if automatic recovery is possible.
Validates API contracts by discovering consumers and ensuring responses match their expectations. Detects breaking changes.
Testing patterns for litefs-py and litefs-django. Use when writing tests, setting up fixtures, understanding test organization, or configuring pytest marks. Triggers: test, pytest, unit test, integration test,...
Backend testing with pytest including fixtures, mocking, async tests, and database testing. Use for FastAPI/Python test implementation.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.