Loading...
Loading...
Found 143 Skills
Check and configure integration testing for services, databases, and external dependencies
Testing patterns for Prowler SDK (Python). Trigger: When writing tests for the Prowler SDK (checks/services/providers), including provider-specific mocking rules (moto for AWS only).
Senior Python developer. Use when writing, reviewing, or refactoring Python code. Enforces idiomatic Python, type hints, and modern patterns.
Guides testing and code quality for kcli. Use when writing tests, running linting, or validating changes before committing.
Use when writing, fixing, editing, or refactoring Python tests. Enforces Clean Code principles—fast tests, boundary coverage, one assert per test.
Mutation Test Runner - Auto-activating skill for Test Automation. Triggers on: mutation test runner, mutation test runner Part of the Test Automation skill category.
Create comprehensive test suites for Frappe Framework v15 applications. Triggers: "create tests", "add tests", "frappe test", "write tests", "test coverage", "/frappe-test". Generates unit tests, integration tests, fixtures, and factory patterns following testing best practices.
Extract raw price dataframe for a test case
Unit testing patterns and best practices. Use when writing isolated unit tests, implementing AAA pattern, designing test isolation, or setting coverage targets for business logic.
Validate code changes by intelligently selecting and running the appropriate test suites. Use this when editing code to verify changes work correctly, run tests, validate functionality, or check for regressions. Automatically discovers affected test suites, selects the minimal set of venvs needed for validation, and handles test execution with Docker services as needed.
GitHub workflow for ToolUniverse - push code safely by moving temp files, activating pre-commit hooks, running tests, and cleaning staged files. Use when pushing to GitHub, fixing CI failures, or cleaning up before commits.
Run git-workspace-review first to understand which tests need updates. Use when updating existing tests, generating new tests for features, enhancing test quality, ensuring detailed coverage, pre-commit validation. Do not use when auditing test suites - use pensive:test-review. DO NOT use when: writing production code - focus on implementation first.