Loading...
Loading...
Found 208 Skills
Test coverage, code quality, defect metrics, and QA KPIs
Generates comprehensive, workable unit tests for any programming language using a multi-agent pipeline. Use when asked to generate tests, write unit tests, improve test coverage, add test coverage, create test files, or test a codebase. Supports C#, TypeScript, JavaScript, Python, Go, Rust, Java, and more. Orchestrates research, planning, and implementation phases to produce tests that compile, pass, and follow project conventions.
Use the open-source free `ReportGenerator` tool for turning .NET coverage outputs into HTML, Markdown, Cobertura, badges, and merged reports. Use when raw coverage files are not readable enough for CI or human review.
Guides the agent through running and writing Python tests with pytest. Triggered when users say "run tests", "write a test", "test this function", "add unit tests", "run pytest", "check test coverage", "debug failing test", "create test fixtures", "mock a dependency", or mention pytest, pytest-asyncio, pytest-cov, testing, unit tests, integration tests, test coverage, or test-driven development.
Shell script testing expertise using bash test framework patterns from unix-goto, covering test structure (arrange-act-assert), 4 test categories, assertion patterns, 100% coverage requirements, and performance testing
A comprehensive verification system for Claude Code sessions.
How to effectively test the application, always use when writing tests
Test-driven development for Laravel with PHPUnit and Pest, factories, database testing, fakes, and coverage targets.
Executes all test suites and reports results with coverage
Analyzes code to identify untested functions, low coverage areas, and missing edge cases. Use when reviewing test coverage or planning test improvements. Generates specific test suggestions with example templates following amplihack's testing pyramid (60% unit, 30% integration, 10% E2E). Can use coverage.py for Python projects.
Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.
Analyze gaps between requirements/features that should be tested and actual test coverage, identifying testing deficiencies and prioritizing test improvements