ln-62-release-publisher
levnikolaevich/claude-code-skills570
levnikolaevich/claude-code-skills570ln-62-release-publisher
Prepares and publishes an explicitly requested tagged GitHub release; does not deploy applications.
Testing Skill
528 Skills in “Testing”, ranked by repository stars. Categories are generated automatically and are for reference only.
AllAI & agents1707Docs & office662Frontend572Testing528Projects & collaboration342Databases & data300DevOps & cloud291Science289Code quality & review235Security225Browser automation217
ln-63-deployment-engineerlevnikolaevich/claude-code-skills570
levnikolaevich/claude-code-skills570ln-63-deployment-engineer
Prepares CI/CD and infrastructure, then executes authorized deployments with health and recovery checks.
ln-64-community-announcerlevnikolaevich/claude-code-skills570
levnikolaevich/claude-code-skills570ln-64-community-announcer
Drafts or publishes authorized, fact-checked GitHub Discussions announcements; does not create releases.
ln-71-operations-investigatorlevnikolaevich/claude-code-skills570
levnikolaevich/claude-code-skills570ln-71-operations-investigator
Diagnoses incidents from operational evidence and proposes recovery; does not change live systems.
ln-72-product-outcome-evaluatorlevnikolaevich/claude-code-skills570
levnikolaevich/claude-code-skills570ln-72-product-outcome-evaluator
Evaluates observed product outcomes against a prior hypothesis; does not run experiments or change user treatment.
audit
oliver-kriska/claude-elixir-phoenix565
oliver-kriska/claude-elixir-phoenix565audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
plugin-dev-workflowoliver-kriska/claude-elixir-phoenix565
oliver-kriska/claude-elixir-phoenix565plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.
reality-verification
tzachbon/smart-ralph557
tzachbon/smart-ralph557reality-verification
This skill should be used when the user asks to "verify a fix", "reproduce failure", "diagnose issue", "check BEFORE/AFTER state", "VF task", "reality check", "check test quality", "mock-only tests", or needs guidance on verifying fixes by reproducing failures before and after implementation, or detecting mock-heavy test anti-patterns.
design
vladikk/modularity552
vladikk/modularity552design
Designs modular high-level architectures from functional requirements and produces design documents for each module. Use when designing a new system, creating architecture documentation, or producing module-level design specs with integration contracts and test specifications.
docker-agent-deploy
docker/skills542
docker/skills542docker-agent-deploy
Use this skill when exposing a Docker Agent as a server (MCP, HTTP API, A2A, ACP, or OpenAI-compatible chat), distributing an agent via an OCI registry with `docker agent share`, or measuring agent quality with `docker agent eval`. Even if the user just says they want to "turn my agent into an MCP server", "let Claude Desktop use my agent", "publish my agent to Docker Hub", "push my agent like an image", or "test my agent in CI", this skill applies. Covers `serve mcp/api/a2a/acp/chat` listen addresses and auth flags, `share push/pull`, eval session JSON format, scoring metrics, and the `--baseline` regression gate.
marketing-os
Yuzzyuk/marketing-os536
Yuzzyuk/marketing-os536marketing-os
A complete marketing department in one skill. Website and landing-page audits with weighted 0-100 scores, copywriting with panel scoring and AI-slop removal, an 18-tactic ad hook engine, GEO/AEO for getting cited by ChatGPT/Perplexity/AI Overviews, paid-ads creative diagnosis and production briefs, email sequences, LinkedIn/X writing, launch playbooks, positioning and offer design, competitor teardowns, app store optimization, honest analytics and test design. Use for ANY marketing task — audit, write, rewrite, diagnose, score, plan, launch, position, price, analyze — whenever the user mentions marketing, growth, conversion, copy, ads, hooks, CPM, ROAS, SEO, GEO, email, social, landing pages, funnels, launches, competitors, brand, positioning, pricing, or app stores, or says "my landing page sucks", "nobody's converting", "why are my CPMs up", "AI doesn't recommend us", "write me 20 hooks". Route via the table inside; fan out subagents for multi-dimensional work. Not for pure engineering, legal, or finance.
accessibility-testing
vibeeval/vibecosystem531
vibeeval/vibecosystem531accessibility-testing
axe-core integration, WCAG 2.2 AA checklist, keyboard navigation testing, screen reader testing, and ARIA pattern validation.
agent-qa-testingvibeeval/vibecosystem531
vibeeval/vibecosystem531agent-qa-testing
Agent davranis testi ve protokol uyumluluk dogrulamasi. Agent'larin tanimli rollerine uygun davranip davranmadigini assertion-based test'lerle olcer. Personality drift, role violation ve output kalite regresyonu tespit eder.
agent-tamagotchivibeeval/vibecosystem531
vibeeval/vibecosystem531agent-tamagotchi
Terminal pet that lives in your statusline. 12 species, 5 stats (DEBUGGING, PATIENCE, CHAOS, WISDOM, SPEED). Reacts to your workflow - happy when tests pass, sad when builds fail, excited during swarm mode. Deterministic species from user ID.
ai-slop-cleanervibeeval/vibecosystem531
vibeeval/vibecosystem531ai-slop-cleaner
Post-implementation cleanup that removes AI-generated bloat while preserving functionality. Runs pass-by-pass with test verification after each pass. Activate after kraken/spark complete a feature, or when a codebase needs hygiene work.
api-patternsvibeeval/vibecosystem531
vibeeval/vibecosystem531api-patterns
API design, versioning, testing, schema validation, and contract testing patterns for REST and GraphQL APIs.
critical-code-reviewer
posit-dev/skills531
posit-dev/skills531critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
pr-createposit-dev/skills531
posit-dev/skills531pr-create
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Activate when the user says "create pr", "make a pr", "open pull request", "submit pr", "pr for these changes", or wants to get their current work into a reviewable PR. Assumes the project uses git, is hosted on GitHub, and has GitHub Actions CI with automated checks (lint, build, tests, etc.). Does NOT merge - stops when CI passes and provides the PR link.
pr-threads-addressposit-dev/skills531
posit-dev/skills531pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
review-testingposit-dev/skills531
posit-dev/skills531review-testing
Review test code for quality, design, and completeness after implementing a feature or fixing a bug. Use when the user asks to "review my tests", "check my test quality", "are these tests good enough", "review testing", or after completing a feature implementation that includes tests. Also use when tests feel brittle, flaky, or superficial. Cross-references production code to find coverage gaps.
r-package-developmentposit-dev/skills531
posit-dev/skills531r-package-development
R package development with devtools, testthat, and roxygen2. Use when the user is working on an R package, running tests, writing documentation, or building package infrastructure.
r-testthatposit-dev/skills531
posit-dev/skills531r-testthat
Best practices for writing R package tests with testthat version 3+. Use this skill when writing or organizing tests for an R package or when improving existing tests that use testthat. It covers test structure and expectations, self-sufficient test design, proper cleanup with withr, fixtures, mocking external dependencies, snapshot testing, and BDD-style describe/it patterns.
r-tidyverse-styleposit-dev/skills531
posit-dev/skills531r-tidyverse-style
Use when the user asks to review or clean up R code for tidyverse style, standardize formatting or names, remove redundant comments or wrappers, or make a behavior-preserving style pass. Also use when writing substantial new R package code if the user requests tidyverse style or the package already follows it. Not for routine small edits or general correctness, security, or test-quality reviews.
testing-compose-in-release-mode
skydoves/compose-performance-skills513
skydoves/compose-performance-skills513testing-compose-in-release-mode
Use this skill to ensure Jetpack Compose performance numbers reflect production reality by measuring against a release variant with R8 enabled, Live Literals disabled, and Compose Compiler reports read from the release output directory. Covers why debug builds lie (interpreted Compose runtime, JIT warmup, Live Literals constant-getters), how to set up a release-with-symbols measurement build, and how to wire Macrobenchmark, Compose Compiler reports, Layout Inspector, simpleperf, and Android Studio Profiler against it. Cited result is roughly 75 percent startup gain and 60 percent frame-render gain debug to release. Use when the developer reports "slow startup", "jank", "dropped frames", "high recomposition count", or quotes timings from `assembleDebug`, Layout Inspector, or `CompilationMode.None`. Use when reviewing a perf bug, setting up a CI perf gate, or before filing a perf regression.