agentsclimarketplace

Test

10,621 rows, by stacks then stars

1,559 of these skill files have been read, by 1,201 distinct authors, and what they tell an agent counted. What Test authors agree on, and what they forbid

  • Test coverage

    opendatadiscovery/odd-team/.claude/skills/test-coverage Skill

    0★ repo

    Run the test-coverage-mapper reducer subagent over the per-node enrichment sidecars + actual test files in the target repo. Verifies sidecar-claimed test files exist; surfaces uncovered behaviours as TEST-GAP-NNN candidates ranked by node criticality (anchored on concepts.yaml's security/performance aggregates); cross-references with `doc-gaps.md` for double-jeopardy findings (undocumented AND untested). Emits `lineage/{repo}/test-map.yaml`.

  • Codebase audit

    Saturate/skills/codebase-audit Skill

    no license0★ repo

    Performs comprehensive codebase audit checking architecture, tech debt, security vulnerabilities, test coverage, documentation, dependencies, and maintainability. Use when auditing a project, assessing codebase health, running security scans, checking for vulnerabilities, reviewing code quality, analyzing tech debt, or asked to audit/analyze the entire codebase.

  • Python pro

    simplevaad-debug/superskills/skills/python-pro Skill

    no license0★ repo

    Use when building Python 3.11+ applications requiring type safety, async programming, or robust error handling. Generates type-annotated Python code, configures mypy in strict mode, writes pytest test suites with fixtures and mocking, and validates code with black and ruff. Invoke for type hints, async/await patterns, dataclasses, dependency injection, logging configuration, and structured error handling.

    The same file is in 3 other repositories

  • Test master

    simplevaad-debug/superskills/skills/test-master Skill

    no license0★ repo

    Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation frameworks; analyzing coverage gaps; performance testing with k6 or Artillery; security testing with OWASP methods; debugging flaky tests; or working on QA, regression, test automation, quality gates, shift-left testing, or test maintenance.

    The same file is in 1 other repository

  • Project alignment

    kennyolofsson23-netizen/claude-code-config/skills/project-alignment Skill

    no license0★ repo

    Align any project with Kenny's global Claude Code setup. Audits test coverage, CI/CD, security, skills usage, and creates a prioritized quality roadmap. Use when opening a project for the first time, after a global setup change, or when the user says "align", "bring up to speed", "audit this project", "quality check", or "what's missing".

  • Property based testing

    kennyolofsson23-netizen/claude-code-config/skills/property-based-testing Skill

    no license0★ repo

    Provides guidance for property-based testing across multiple languages and smart contracts. Use when writing tests, reviewing code with serialization/validation/parsing patterns, designing features, or when property-based testing would provide stronger coverage than example-based tests.

    The same file is in 6 other repositories

  • Qa

    kennyolofsson23-netizen/claude-code-config/skills/qa Skill

    no license0★ repo

    Full QA pass: run all tests, check types, catch regressions, write missing tests. Use when the user says "run tests", "QA", "verify changes", "check for regressions", "test everything", or "make sure it works".

  • Security review

    kennyolofsson23-netizen/claude-code-config/skills/security-review Skill

    no license0★ repo

    Security-focused differential code review for PRs, commits, and diffs. Calculates blast radius, checks test coverage, models attacks, and generates markdown reports. Based on Trail of Bits methodology. Use for PR reviews, commit audits, and pre-deployment diff checks. For full codebase audits, use /security-audit instead.

  • Test write

    kennyolofsson23-netizen/claude-code-config/skills/test-write Skill

    no license0★ repo

    Write tests for the Travmaskinen codebase — backend (pytest, async, FastAPI), frontend (Vitest + React Testing Library), or E2E (Playwright). Use this skill whenever writing new tests, adding test coverage, implementing TDD red-green-refactor cycles, or when the user says "write tests", "add tests", "test this", "cover this", "TDD", or asks for test coverage on any module. Also triggers when implementing new features that need tests first (TDD flow).

  • Webapp testing

    kennyolofsson23-netizen/claude-code-config/skills/webapp-testing Skill

    no license0★ repo

    Test and debug local web applications using Playwright. Captures screenshots, verifies UI behavior, checks browser logs, and runs E2E test scenarios. Use when the user says "test the app", "check the UI", "take a screenshot", "debug the frontend", "run E2E tests", "verify the page works", or "Playwright test".

  • Edge case challenger

    taewanu/skills/skills/in-progress/edge-case-challenger Skill

    0★ repo

    Challenge a working assumption or a settled decision that nobody re-questions, by running a fixed set of probes against the ONE decision, not by free-associating about what could break. Use when something has worked long enough to feel settled and the user wants it pressure-tested: '여태 이렇게 해왔는데', '이 가정 맞나', '전제를 다시 보자', '엣지 케이스', '스케일업하면?', '이거 언젠가 터지지 않나', 'pressure-test this assumption', 'what breaks at scale', 'challenge this decision', 'is this premise still true', 'stress this at 10x', or when a decision passed review on one axis and no one checked the others.

  • Ios sims

    jimmynotjames/simple-recurring-budgets/.claude/skills/ios-sims Skill

    no license0★ repo

    iOS simulator setup, management commands, SRB_SIM_MAX concurrency tuning, two-pass test architecture, and AM/PM time workaround for this repo. Invoke when setting up a fresh clone, debugging simulator failures, adjusting parallelism, or writing UI tests that assert time strings.

  • Swift testing

    jimmynotjames/simple-recurring-budgets/.claude/skills/swift-testing Skill

    no license0★ repo

    Writes and migrates Swift Testing framework tests with @Test, @Suite, #expect, #require, confirmation, traits, withKnownIssue, Attachment.record, processExitsWith exit tests and capture lists, Test.cancel, Issue.record warnings/manual failures, XCTest-to-Swift Testing migration, XCUITest UI-test boundaries, performance/snapshot boundaries, mocking, async patterns, and test organization. Use when writing tests, converting XCTest assertions such as XCTUnwrap or XCTFail, reviewing advanced Swift Testing API availability, or deciding when to keep XCTest/XCUITest.

  • Ios sims

    jimmynotjames/simple-recurring-budgets/.cursor/skills/ios-sims Skill

    no license0★ repo

    iOS simulator setup, management commands, SRB_SIM_MAX concurrency tuning, two-pass test architecture, and AM/PM time workaround for this repo. Invoke when setting up a fresh clone, debugging simulator failures, adjusting parallelism, or writing UI tests that assert time strings.

  • Swift testing

    jimmynotjames/simple-recurring-budgets/.cursor/skills/swift-testing Skill

    no license0★ repo

    Writes and migrates Swift Testing framework tests with @Test, @Suite, #expect, #require, confirmation, traits, withKnownIssue, Attachment.record, processExitsWith exit tests and capture lists, Test.cancel, Issue.record warnings/manual failures, XCTest-to-Swift Testing migration, XCUITest UI-test boundaries, performance/snapshot boundaries, mocking, async patterns, and test organization. Use when writing tests, converting XCTest assertions such as XCTUnwrap or XCTFail, reviewing advanced Swift Testing API availability, or deciding when to keep XCTest/XCUITest.

  • Test web code

    wjb127/claude-skills/test-web-code/skills/test-web-code Skill

    0★ repo

    Generate and run Unit + Integration + E2E tests for a web project. Every scenario ships Happy / Sad / Bad / Ugly variants, so happy-path-only suites are impossible. Production-first E2E with no automation bypasses — no fake-green tests. 웹 프로젝트 통합 테스트 생성·실행. 해피패스 금지, 우회 없는 프로덕션 E2E.

  • Flaky test detector

    Evan-Daruwalla/claude-skill-suite/flaky-test-detector Skill

    0★ repo

    Run a test command N times and classify its stability: STABLE-PASS (every run exited 0), STABLE-FAIL (every run failed IDENTICALLY — a consistently red test is a bug, not flake, and is labeled as such), or FLAKY (exit codes varied across runs — the finding). Records each run's exit code + wall-clock duration, prints a per-run table + pass/fail rates, and can save each run's stdout+stderr to numbered files for diffing (--keep-logs). The harness is deterministic; the subject under test may not be — that is the point. Use when the user says "is this test flaky", "flaky test", "detect flakiness", "does this test pass reliably", "run it N times", "why does this test fail intermittently", or wants a test/command re-run repeatedly to check for non-determinism. Deterministic harness, zero dependencies, no model calls.

  • Golden lock

    Evan-Daruwalla/claude-skill-suite/golden-lock Skill

    0★ repo

    Freeze ANY output as a byte-exact golden baseline and diff on change — one engine over three inputs: a command's stdout, a fixture file, or a prompt/text asset. "freeze" records the baseline (output.txt + meta.json under .golden/); "check" re-produces it and fails with a line-numbered diff on any drift, comparing bytes AND exit code. Generalizes frozen-regression-test discipline (an output pinned byte-exact) to arbitrary outputs. Use when the user says "freeze this output", "golden test", "lock the baseline", "snapshot freeze", "did the output change", "prompt regression", "guard against output drift", or wants a fixture/prompt/command pinned so any change is a failing diff. Deterministic, zero dependencies, no model calls.

  • Connecting to data source

    dkmqflx/claude-tools/.claude/skills/connecting-to-data-source Skill

    no license0★ repo

    Create and troubleshoot AWS Glue connections to JDBC databases (Oracle, SQL Server, PostgreSQL, MySQL, RDS), Redshift, Snowflake, and BigQuery. Gathers connection hints from user, discovers existing connections and RDS/Redshift candidates, registers credentials in Secrets Manager or IAM DB auth, configures VPC, and tests. Triggers on: connect to database, set up Glue connection, register data source, connect to Snowflake/BigQuery/RDS, connection timeout, test connection, troubleshoot connection. Do NOT use for moving data (use ingesting-into-data-lake), creating tables (use creating-data-lake-table), queries (use querying-data-lake), catalog exploration (use exploring-data-catalog), or SaaS (Salesforce, ServiceNow, SAP, MongoDB, Kafka).

  • Fastapi best practices

    dkmqflx/claude-tools/.claude/skills/fastapi-best-practices Skill

    no license0★ repo

    Use when writing, reviewing, or refactoring FastAPI code — endpoints, APIRouter, query/path parameters, dependencies (Depends), Pydantic request/response models, error handling, async def vs def, lifespan events, streaming, background tasks, settings, middleware, or CORS. Triggers on FastAPI backend work, route design, or API code review. For auth/security see fastapi-security; for tests see fastapi-testing.

    The same file is in 1 other repository

  • Fastapi testing

    dkmqflx/claude-tools/.claude/skills/fastapi-testing Skill

    no license0★ repo

    FastAPI testing best practices. Use when writing or reviewing tests for a FastAPI app — TestClient, dependency_overrides, async httpx clients. Triggers on TestClient, AsyncClient, ASGITransport, dependency_overrides, or pytest test files for FastAPI endpoints.

    The same file is in 1 other repository

  • Nestjs testing

    dkmqflx/claude-tools/.claude/skills/nestjs-testing Skill

    no license0★ repo

    NestJS testing best practices (unit and e2e). Use when writing or reviewing NestJS tests — Test.createTestingModule, mocking providers, controller/service unit tests, or e2e with supertest. Triggers on TestingModule, createTestingModule, overrideProvider, or supertest.

    The same file is in 1 other repository

  • Testing patterns

    dkmqflx/claude-tools/.claude/skills/testing-patterns Skill

    no license0★ repo

    Vitest testing patterns for this project. Automatically applied when writing unit/integration tests for components, custom hooks, Server Actions, and utility functions.

  • Review

    AI-Driven-School/aiki/.claude/skills/review Skill

    0★ repo

    Run code review against design documents, checking acceptance criteria, security, performance, and test coverage. Use when reviewing implementation quality or running /review.

  • Test

    AI-Driven-School/aiki/.claude/skills/test Skill

    0★ repo

    Generate E2E and unit test code from requirements using Playwright, delegated to Codex. Use when writing tests, checking acceptance criteria coverage, or running /test.

  • Skill battle

    bwitlin/claude-skills/plugins/skill-battle/skills/skill-battle Skill

    0★ repo

    Run multiple skills on the same task in parallel and compare outputs side by side. A creative pitch room -- give it a brief, and it finds skills (local + trusted community repos) to work on it independently, then presents all outputs for comparison. Use when asked to "skill battle", "compare skills", "run multiple skills", "pitch room", "get different takes", "split test this", "give me options", or any request to see how different skills handle the same task. Great for generating variants for split testing -- headlines, email copy, ad creative. Best for subjective work where different perspectives add real value. Not useful for tasks with one right answer (bug fixes, migrations, config changes). Always use this skill instead of manually running skills one at a time when the user wants to compare outputs.

  • Test cases

    latuconsinafr/claude-code-config/skills/test-cases Skill

    no license0★ repo

    Use when you need to document E2E test cases for a feature or bug fix that can't be covered by unit or integration tests alone. Auto-detects ticket from branch name. Reuses codebase context from /plan if already run; falls back to git diff + explorer when invoked standalone. Outputs to a markdown file by default.

  • Asyncpg live vs mock shape

    Ed3Design/ed3design-skill-bundles/async-forensik/skills/asyncpg-live-vs-mock-shape Skill

    0★ repo

    Use when writing pytest mocks for asyncpg-backed endpoints where the column type causes mock-vs-live divergence (SUM/COUNT/AVG → Decimal; JSONB → str; UUID → UUID-object; INET → str). asyncpg returns raw PG-types that don't match naive intuition — mocks with the "natural" dict/int/float pass shape-tests but the real DB-call fails live. Trigger on phrases like "asyncpg mock test", "asyncpg JSONB mock", "asyncpg returns string for JSONB", "TypeError Decimal float", "AttributeError str object no attribute keys", "mock-and-live diverge for asyncpg". Do NOT load for psycopg-2-based tests (different driver, auto-coerces JSONB), for SQLAlchemy ORM tests (the ORM coerces types), or for asyncpg connections with `set_type_codec('jsonb', ...)` registered (the codec handles conversion).

  • Aggregate code review after tdd tasks

    Ed3Design/ed3design-skill-bundles/code-quality/skills/aggregate-code-review-after-tdd-tasks Skill

    0★ repo

    Use when implementing a multi-task TDD plan via `superpowers:subagent-driven-development` AND all individual tasks have already passed their per-task two-stage review. Per-task reviews check one commit against one task — they cannot catch cross-commit drift that only appears when reading the full feature end-to-end. Triggers a final aggregate review looking for: state-machine/algorithm-order drift between spec and code, naming-inconsistency across commits, end-to-end data-flow integrity, commit-message honesty, pre-commit-hook coverage gaps (lazy imports), test-suite cohesion. Trigger phrases like "Tasks 1-N all done", "aggregate review before live-run", "cross-commit drift check", "verify end-to-end behavior against spec". Do NOT load for single-commit reviews, per-task reviews within SDD, branches with <3 atomic feature-commits, or hotfixes without spec-text target.

  • Code review findings als red tests

    Ed3Design/ed3design-skill-bundles/code-quality/skills/code-review-findings-als-red-tests Skill

    0★ repo

    Use when a code-review subagent (e.g. feature-dev:code-reviewer) has returned Critical/Important findings on a feature commit and you're about to write fixes. Standard default is "direct-fix, no new test". This skill says: each finding is itself a test case — write a RED test that shows the bug behavior, then GREEN fix. Prevents regressions + documents the bug pattern for future reviews. Trigger on phrases like "fix code-review findings", "implement Critical fix", "review subagent found C1/I1/I2", "convert reviewer output to fix", "close review cycle". Do NOT load for trivial style findings (typo, unused-import), for findings without a reproducible code path (perf hints, future-proofing), for code where TDD was consciously skipped (user-confirmed), or when the subagent had NO findings.

  • Ga skill edit tdd workflow

    Ed3Design/ed3design-skill-bundles/code-quality/skills/ga-skill-edit-tdd-workflow Skill

    0★ repo

    Use when editing or expanding an already-GA-promoted skill (suffix-less name, banner says PROMOTED) to add a new capability/class/feature. Different from `skill-tdd-promotion-workflow` which covers DRAFT→GA. This skill covers GA→GA+Capability — the failure mode is silent-rename-or-expand without RED-test for the new capability (Iron-Law violation). Trigger on phrases like "extend skill with X", "add a new class to an existing skill", "extend asyncpg-skill with JSONB", "rename GA skill + extend capability", "skill rename with content expansion", "Cycle-2 capability for promoted skill". Do NOT load for new skill from scratch (`superpowers:writing-skills`), for DRAFT→GA promotion (`skill-tdd-promotion-workflow`), for minor edit without new capability (just edit), or when the target skill doesn't exist.

  • Pytest venv first triage

    Ed3Design/ed3design-skill-bundles/code-quality/skills/pytest-venv-first-triage Skill

    0★ repo

    Use when pytest shows multiple failures or errors (especially ModuleNotFoundError clusters) and you're about to dig into individual test fixes. ALWAYS check the Python environment FIRST — `which python3` vs `venv/bin/python3` — before debugging individual tests. System-Python frequently lacks project deps (cachetools, asyncpg, etc.) while project venv has them. Trigger on phrases like "pytest shows many failures", "test errors after pull", "these tests were green yesterday", "ModuleNotFoundError multiple files", "pre-existing failures", "tests broken without code change", "ImportError test sweep". Do NOT load for single-test-fail debugging (use systematic-debugging directly), for Python projects without venv (no env mismatch possible), or for failures with clear test-logic bugs (e. g. assertion errors with concrete values).

  • Static source bug class coverage test

    Ed3Design/ed3design-skill-bundles/code-quality/skills/static-source-bug-class-coverage-test Skill

    0★ repo

    Use when adding regression-test coverage for a bug-class that manifests as a repeated source-code pattern across multiple call-sites in the same file or codebase, NOT a single localized bug. Pattern: write a static-source-inspect-test that reads the source file directly via `Path(__file__).resolve().parents[N] / "src/file.py"`, extracts pattern candidates via regex (e.g. all triple-quoted SQL blocks containing certain tokens), and asserts each candidate contains the fix-marker. Critical: include a whitelist-skip for f-string templates with externalized variables that receive the fix at their definition site. Trigger on phrases like "write bug-class coverage test", "static source inspect test", "regression guard for the same bug pattern in multiple call-sites", "why not just endpoint mocks for all 4 spots?". Do NOT load for single-call-site bugs, bug classes not recognizable in the source pattern, or files with complex multi-layer f-string nesting where false-positive whitelisting becomes unreliable.

  • Production seed vs demo seed split

    Ed3Design/ed3design-skill-bundles/schema-discipline/skills/production-seed-vs-demo-seed-split Skill

    0★ repo

    Use when about to push a Code-Repo with seed/fixture-data containing real personal/customer/tenant data to a Remote (GitHub, GitLab) — even private. Triggers on phrases like "push repo for the first time", "create new private repo", "set up GitHub remote for <project>", "commit seed.py", "tenant data in code", "customer data in test data", "GDPR test data". Do NOT load for repos without personal data (pure tech repos like ESP32-firmware), for already-pushed repos (then it's git-filter-repo territory, different skill), or for ephemeral test-data without real-person reference. Encodes a property-management push-session pattern: 26 commits contained real tenant data + a .env demo credential; without the pre-push scan everything would have landed on GitHub.

  • Skill tdd promotion workflow

    Ed3Design/ed3design-skill-bundles/skill-system-meta/skills/skill-tdd-promotion-workflow Skill

    0★ repo

    Use when promoting an existing DRAFT/STUB skill (suffix `-DRAFT` or `-STUB` in `name:` field, OR description starts with "STUB —") to GA (auto-discoverable). Different from `superpowers:writing-skills` which covers CREATE-from-scratch — this skill covers the LIFECYCLE-STAGE from "skeleton-exists" to "production-ready". Requires Agent/Task-tool for parallel RED+GREEN subagent-Dispatch (Step 3) — if the caller does NOT have Agent-tool (e.g. running as a general-purpose-subagent themselves), STOP and report-up; do NOT silently fall back to name-rename-only. Trigger on phrases like "promote this DRAFT skill", "TDD for the remaining STUBs", "make it auto-discoverable", "skill promotion cycle", "release skill from -DRAFT", "TDD promotion cycle for N skills". Do NOT load for creating a new skill from scratch (use `superpowers:writing-skills`), for editing GA-skills (just edit), when no DRAFT/STUB-suffix exists (skill is already GA), or when target skill file does not exist (no work to do).

  • Product pressure test

    isanthoshgandhi/santhoshstack/skills/product-pressure-test Skill

    0★ repo

    Product pressure test before you build. Two modes: Startup (6 YC-style forcing questions that expose demand reality, status quo, target user, narrowest wedge, observation, and future-fit) and Builder (generative brainstorming for side projects, hackathons, and open source). Produces a design doc. Invoke when the user describes a new idea, asks whether something is worth building, or wants to pressure-test a feature before writing code. Trigger on: is this worth building, pressure test this, product review, office hours, I have an idea, should I build this, help me think through this.

  • Pressure test

    robmcquade/claude-skills/pressure-test Skill

    0★ repo

    Stress-test substantive work — surface strengths, weaknesses, hidden assumptions, failure modes, and adjacent ideas, then return prioritized, actionable fixes (each weakness plus how to fix it). Recommends the fixes; does not produce the rewrite (that is /improve's job). User-invoked only. In Claude Code a deterministic orchestrator auto-escalates security, PII, and credential artifacts to deep, fans out fresh-context subprocess critics with schema-forced output, firewalls sensitive content away from web search, runs an independent verifier, and emits a verified findings manifest; without a shell it runs the same lenses inline and discloses that the enforced gate did not run. Use on durable artifacts (files, frameworks, memos, redlines, decisions, contracts, public content, prompts, proposals) and multi-step work where early choices constrain later ones. Apparent narrowness ('just review this') can mask real stakes. Skip single-fact lookups and content already endorsed and ready to execute.

  • Go idioms

    Cadasto/go-coding-plugin/skills/go-idioms Skill

    0★ repo

    Modern idiomatic Go (the `modernize` analyzer set). This skill should be used when the user writes, reviews, or modernizes Go and wants current-version idioms — range-over-int, `min`/`max`, `slices`/`maps`, `strings.Cut`, `cmp.Or`, `sync.OnceFunc`, iterators, `slog.LogAttrs`, `new(expr)` (Go 1.26), dropped loop-var copies. Framed so advice equals tooling (`go fix ./...` on Go 1.26, or `golangci-lint --enable-only=modernize`). Errors→`go-errors`, concurrency→`go-concurrency`, tests→`go-testing`. Not for golangci-lint configuration (use `go-linting`) or non-Go languages.

  • Go testing

    Cadasto/go-coding-plugin/skills/go-testing Skill

    0★ repo

    Idiomatic Go testing. This skill should be used when the user writes or reviews Go tests, benchmarks, or fuzz targets — table-driven tests, `t.Parallel`, `testing.B.Loop`, the race detector, goroutine-leak detection, `testing/synctest` for time/concurrency, fuzzing, or golden files. Pair with `go test -race`. Not for non-Go test frameworks; error-wrapping belongs to `go-errors`.

  • Property based testing

    TomerAberbach/claude-config/skills/property-based-testing Skill

    0★ repo

    Use when writing, reviewing, or modifying property-based tests, such as those using `fast-check`, or when asked to add test coverage.

  • Reconcile tests

    TomerAberbach/claude-config/skills/reconcile-tests Skill

    0★ repo

    Add, update, or delete tests for changes in the current commit.

  • Hello world

    twisker/ipman/tests/e2e/fixtures/skills/claude-code/hello-world Skill

    0★ repo

    Minimal test skill for E2E testing

  • Hello world

    twisker/ipman/tests/e2e/fixtures/skills/openclaw/hello-world Skill

    0★ repo

    Minimal test skill for E2E testing

  • Test driven development

    chenwei791129/agent-skills/hermes-skills/superpowers/test-driven-development Skill

    0★ repo

    Use when implementing any feature or bugfix, before writing implementation code

  • Test pattern

    bogheorghiu/ex-cog-dev/vasana-system/skills/test-pattern Skill

    0★ repo

    Tests whether patterns actually work — trigger, emerge, and produce value. Use when (1) user wants to verify a pattern before relying on it, (2) user runs /test-pattern command, (3) a pattern was just recorded and needs verification, or (4) user suspects a pattern isn't working as expected.

  • Python testing tdd

    JoseVelazcoH/python-skills/skills/python-testing-tdd Skill

    0★ repo

    Trigger: write tests, pytest, TDD, red-green-refactor, fixtures, mocks, parametrize, coverage, test first. Drive Python features test-first with quality pytest patterns.

  • Sap cap test

    Fab2295/sap-skills/skills/sap-cap-test Skill

    0★ repo

    Test-only skill for SAP CAP Node.js projects. Its sole purpose is to scaffold and run automated tests using `cds test` (Node.js test runner wrapper) and, when (and only when) explicitly requested by the user, produce coverage with `c8`. The skill writes test files under `test/` (or the project's existing test folder), executes them, and emits two possible report files at the project root: - `CAP-TEST-REPORT.md` — successful run summary (always) - `CAP-TEST-FAILURE.md` — failure report (only if a test fails) Use when the user asks to: - "cria testes", "gera teste para X", "scaffold tests" - "roda os testes", "executa cds test", "run tests" - "testa o serviço X", "cobertura c8" (coverage mode — must be explicit) Strict negatives — this skill NEVER: - edits production code (`srv/**`, `db/**`, `app/**`, `package.json`, `.cdsrc.json`, `mta.yaml`, `xs-security.json`) — it only writes inside the test folder - implements features, refactors, fixes bugs, changes business logic - runs `git add`, `git commit`, `git push`, `git merge`, `git rebase`, `git reset`, `git checkout` of source files, or any git mutation - installs dependencies on its own (it may *propose* `npm i -D c8` and wait for human approval; it does not run it unsolicited) - generates coverage unless the user explicitly opts in - touches the build output (`gen/`, `coverage/`, `dist/`) Scope: SAP CAP Node.js only. If the project is CAP Java or non-CAP, the skill refuses with an explicit message.

  • Pre push test

    chienchuanw/chuan-skills/plugins/git/skills/pre-push-test Skill

    no license0★ repo

    Use when the user wants to prevent broken code from being pushed, block git push when tests fail, run tests before push, set up push protection, or add a safety net against pushing untested code. Covers any request to gate pushes on test results — whether they mention "hook", "pre-push", or just describe wanting to stop bad code from reaching the remote. Also handles auto-fix/auto-repair of test failures before push. Trigger for: "block push if tests fail", "run tests before pushing", "protect branch from broken pushes", "stop pushing untested code", "catch failures before they reach remote", or any test-gated push workflow regardless of language (npm, pnpm, cargo, go, pytest, etc).

  • Running integration tests

    pacho-h/ssep/skills/running-integration-tests Skill

    0★ repo

    Authors and runs tests across the test pyramid — unit, FE↔BE integration, and end-to-end browser scenarios — using Playwright MCP and runners (jest, vitest, mocha). Use when verifying multi-layer behavior or for "e2e 테스트", "integration 테스트", "통합 테스트", "playwright로 검증", "브라우저에서 직접 확인", "백엔드-프론트 연동", "API 통합 테스트", "staging 검증", "배포 후 검증", "smoke test", or when a feature crosses boundaries (API + UI + DB). Also triggers when verifying a deployed feature or when a PR test plan has unchecked browser/API items. Triggers even when only one boundary is crossed and a manual Playwright click was performed; manual verification proves the path works once but does not produce a codified regression, and integration-tier surprises cluster at exactly the boundary that "looked fine" during manual checks. Decides which test level fits, sets up infra, writes tests, runs them, reports failures with diagnostic context. Distinct from superpowers:test-driven-development (unit-level TDD); handles integration and e2e tiers.

  • Frappe dev

    prilk-consulting/frappe-agent-kit/skills/frappe-dev Skill

    0★ repo

    Frappe Framework core development reference. Use proactively for DocType controllers, server scripts, whitelisted APIs, database operations, hooks.py, permissions, background jobs, caching, desk client scripts, Jinja/print formats, and custom app structure on Frappe v15+ and ERPNext. Not for React/Vue SPA frontends (use frappe-frontend), portal/website pages (use frappe-portal), or writing tests (use frappe-test).

  • Frappe test

    prilk-consulting/frappe-agent-kit/skills/frappe-test Skill

    0★ repo

    Writing and running tests for Frappe and ERPNext apps. Use for FrappeTestCase patterns, test_records.json fixtures, test dependencies, permission testing, bench run-tests invocations, and test isolation gotchas.

  • Systematic debug fix

    quanpersie2001/pulse/skills/systematic-debug-fix Skill

    no license0★ repo

    Use when the user asks for root-cause-first debugging of bugs, test failures, flaky behavior, build issues, or integration defects with tracked verification and regression lock-down.

  • Webapp testing

    JamesPrial/skills/skills/webapp-testing Skill

    no license0★ repo

    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

    The same file is in 45 other repositories

  • Ai regression testing

    goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/ai-regression-testing Skill

    no license0★ repo

    Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code.

    The same file is in 6 other repositories

  • Test app automation

    goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/awesome-claude-skills/composio-skills/test-app-automation Skill

    no license0★ repo

    Automate Test App tasks via Rube MCP (Composio). Always search tools first for current schemas.

    The same file is in 5 other repositories

  • Webapp testing

    goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/awesome-claude-skills/webapp-testing Skill

    no license0★ repo

    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

    The same file is in 45 other repositories

  • Test app automation

    goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/composio-skills/test-app-automation Skill

    no license0★ repo

    Automate Test App tasks via Rube MCP (Composio). Always search tools first for current schemas.

    The same file is in 5 other repositories

  • Cpp testing

    goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/cpp-testing Skill

    no license0★ repo

    Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.

    The same file is in 7 other repositories

  • Csharp testing

    goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/csharp-testing Skill

    no license0★ repo

    C# and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices.

    The same file is in 1 other repository

  • Django tdd

    goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/django-tdd Skill

    no license0★ repo

    Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.

    The same file is in 8 other repositories