All categories
Testing & QA
Unit tests, integration tests, E2E, QA, validation, and test automation
- 29,138
- 1,215
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse testing & qa skills
Showing 385–408 of 29,138 skills
- Commit 49Stage changes and create git commits with conventional commit messages. Use when asked to "commit", "stage and commit", "save changes", or after completing implementation tasks. Alias for /git/cm.Votes: 0GitHub stars: 2
- Command Pattern TypescriptRepresent actions as objects for decoupled invocation, queue/schedule/retry/audit, and optional undo/redo; TS/Node async-friendly command bus; trade-offs vs Strategy/CoR/Events.Votes: 0GitHub stars: 2
- Cogames Variant DebugDebug CoGames mission or variant regressions by comparing branch vs main. Use when behavior changes or a `cogames play` command regresses.Votes: 0GitHub stars: 2
- Coding PythonApply this skill when generating Python codeVotes: 0GitHub stars: 2
- Codex Validationbrainbaseにおける_codex正本とプロジェクト側参照の整合性を検証するロジック。リンク切れ、誤編集、必須項目の検証を実施。_codexの整合性をチェックする際に使用。Votes: 0GitHub stars: 2
- Codex Pr Review LoopUse when managing Codex review iterations for a PR and you must enforce preflight risk-layer checks and post-merge learning capture.Votes: 0GitHub stars: 2
- Codebase Analysis 2Analyze codebase for existing implementations, test coverage, and code patterns. Use when checking what's already implemented, finding related code, or assessing test coverage for features.Votes: 0GitHub stars: 2
- Code VerificationMulti-agent code verification workflow using a main agent and sub-agent loop. Use when verifying code against requirements, acceptance criteria, or quality standards. Triggers on requests to verify, validate, or check code against specifications, checklists, or instructions.Votes: 0GitHub stars: 2
- Code Testing PlanningAnalyzes existing code and specs to identify missing test coverage and formulate a robust Testing Plan. Used for adding regression tests, increasing coverage, and verifying legacy code behavior.Votes: 0GitHub stars: 2
- Code Testing ImplementationOrchestrates the Testing Strategy & Implementation process (Planning -> Execution -> Closing). Manages the workflow by invoking specialized sub-skills like code-testing-planning, tdd-refactoring, and tdd-audit. Used for (1) adding missing coverage for legacy code, (2) reproducing reported bugs with regression tests (xfail), and (3) verifying edge cases or error handling for existing logic.Votes: 0GitHub stars: 2
- Code TestRun tests to validate changes. Use after implementing features, fixing bugs, or before commits. Defaults to 'just test-local' which runs without external dependencies (recommended for local development).Votes: 0GitHub stars: 2
- Code Task GeneratorThis sop generates structured code task files from rough descriptions, ideas, or PDD implementation plans. It automatically detects the input type and creates properly formatted code task files following Amazon's code task format specification. For PDD plans, it processes implementation steps one at a time to allow for learning and adaptation between steps.Votes: 0GitHub stars: 2
- Code Simplifier 15Refine code for clarity and maintainability while preserving functionalityVotes: 0GitHub stars: 2
- Code Reviewer Business LogicCorrectness Review: reviews domain correctness, business rules, edge cases, and requirements. Uses mental execution to trace code paths and analyzes full file context, not just changes.Votes: 0GitHub stars: 2
- Code Reviewer 4You are an expert code reviewer. When reviewing code, follow this workflow: 1. **Analyze**: Review the staged changes or specific files provided. Ensure that the changes are scoped properly and represent minimal changes required to address the issue. 2. **Style**: Ensure code follows the project's conventions and idiomatic patterns as described in the `GEMINI.md` file. 3. **Security**: Flag any potential security vulnerabilities. 4. **Tests**: Verify that new logic has corresponding test ...Votes: 0GitHub stars: 2
- Code Reviewer 10Expert code review for Java/Spring Boot and TypeScript/Next.js codebases. Performs multi-dimensional reviews covering correctness, security, testability, architecture, and maintainability. Automatically delegates to specialized skills when detecting: security vulnerabilities → security-expert, auth/Keycloak → keycloak-skill, Java test quality → java-test-engineer, TypeScript/React test quality → ts-test-engineer, architecture issues → architecture-tech-lead, frontend patterns → frontend-desig...Votes: 0GitHub stars: 2
- Code Review Checklist 5Systematic code review using quality gates, SOLID principles, error handling patterns, and test coverage analysis. Provides structured feedback with severity levels and actionable improvements.Votes: 0GitHub stars: 2
- Code Review 84Senior frontend code review for Vue/TypeScript. Use when reviewing PRs, checking code quality, or validating against project conventions.Votes: 0GitHub stars: 2
- Code Review 7Perform a thorough code review with Staff Software Engineer rigor, grounded in ticket context and relevant documentation.Votes: 0GitHub stars: 2
- Code Review 117Use when reviewing code changes or conducting PR reviews.Votes: 0GitHub stars: 2
- Code Review 114A skill for reviewing software changes. It helps analyze differences between git references (branches, tags, commits), review history, and provide feedback to ensure code quality and adherence to project conventions.Votes: 0GitHub stars: 2
- Code Refactoring 4Simplify and refactor code while preserving behavior, improving clarity, and reducing complexity. Use when simplifying complex code, removing duplication, or applying design patterns. Handles Extract Method, DRY principle, SOLID principles, behavior validation, and refactoring patterns.Votes: 0GitHub stars: 2
- Code Refactor 4Systematic refactoring of codebase components through a structured 3-phase process. Use when asked to refactor, restructure, or improve specific components, modules, or areas of code. Produces research documentation, change proposals with code samples, and test plans. Triggers on requests like "refactor the authentication module", "restructure the data layer", "improve the API handlers", or "clean up the payment service".Votes: 0GitHub stars: 2
- Code Quality WorkflowMandatory code quality workflow that must run after ANY code changes. Use after creating/editing files, before commits, or when fixing errors. Keywords - testing, linting, formatting, typecheck, quality gates, workflow.Votes: 0GitHub stars: 2