#SkillRepo stars
- 913QA Testing StrategyFreddy-CHEN-ux/00_claude_skillsRisk-based quality engineering test strategy across unit, integration, contract, E2E, performance, and security testing with shift-left gates, flake control, CI economics, and observability-first debugging.8
- 914Resource LimitingFreddy-CHEN-ux/00_claude_skillsProtect shared servers from resource exhaustion during development tasks. Provides commands and best practices for limiting CPU, RAM, and I/O usage when running tests, migrations, and builds on shared servers.8
- 915Router OperationsFreddy-CHEN-ux/00_claude_skillsMaster orchestration for routing QA, testing, DevOps, observability, and git workflow questions through 15 operational skills8
- 916SdlcFreddy-CHEN-ux/00_claude_skillsSDLC workflow automation that implements features using TDD skill, runs test-runner skill, and prepares commit commands for user review. Use when user provides a spec/plan for a new feature. Workflow: (1) invokes test-driven-development skill with spec, (2) invokes test-runner skill, (3) prepares git commands for user to execute manually.8
- 917Test Data Patternsvnovakovits/claude-skillsApply the family of test arrangement patterns — Test Data Builder (Nat Pryce & Steve Freeman, GOOS 2009), Object Mother (Peter Schuh, popularised by Martin Fowler 2006), Arrange-Act-Assert (Bill Wake, 2001), Given-When-Then (Dan North, 2006), and chained Test Fixtures — that keep test setup readable, expressive, and robust to change. Covers fluent builders with sensible defaults, semantic builder methods, the Builder + Mother combination, AAA vs GWT, when to introduce a builder, anti-patterns (constructor-with-twelve-params, mystery guests, irrelevant setup), and the project's `Fixture.Given()5
- 918Test Driven Developmentvnovakovits/claude-skillsApply Test-Driven Development to drive outside-in design in small steps. Centers on the London/mockist school (Freeman & Pryce's GOOS, Sandro Mancuso's outside-in teaching) with Kent Beck's classical foundations and Mark Seemann's pragmatic heuristics. Covers sociable vs solitary unit tests and when to prefer each (anticipated refactoring → sociable). Use when starting a new feature, designing object interactions, building a vertical slice end-to-end, deciding what to test next, choosing the test boundary before refactoring, or rescuing a design that resists testing.5
- 919Test FixerFreddy-CHEN-ux/00_claude_skillsMANDATORY when: tests fail, CI fails, CI/CD fails, ci.yml fails, user provides CI log URL. Investigates failures, fixes iteratively until passing.8
- 920Test RunnerFreddy-CHEN-ux/00_claude_skillsMANDATORY skill for running tests and lint after EVERY code change. Focuses on adherence to just commands and running tests in parallel. If tests fail, use test-fixer skill.8
- 921Test TwilioFreddy-CHEN-ux/00_claude_skillsPlace Twilio test calls. Use when user invokes /test-twilio.8
- 922Test Voice ReportFreddy-CHEN-ux/00_claude_skillsTest report generation with TEXT transcripts (NOT real calls). For real Twilio calls, use twilio-test-call instead.8
- 923Test WriterFreddy-CHEN-ux/00_claude_skillsMANDATORY - INVOKE BEFORE writing ANY test code (def test_*, class Test*). Prevents brittle tests. Read this skill first, then write tests.8
- 924TestingFreddy-CHEN-ux/00_claude_skillsRun tests before and after changes. Only add tests for complex logic, not boilerplate. Database tests matter most.8
- 925Testing Anti PatternsFreddy-CHEN-ux/00_claude_skillsUse to avoid critical testing mistakes. Five Iron Laws: Never test mock behavior, Never add test-only methods, Never mock without understanding, Always integration test, Always test error paths.8
- 926Testing Skills with SubagentsFreddy-CHEN-ux/00_claude_skillsUse to validate process documentation. Apply TDD to skill writing: RED (run without skill, document failures) → GREEN (write skill) → REFACTOR (close loopholes). Test under pressure: time constraints, sunk cost, exhaustion, authority.8
- 927To Ticketsvnovakovits/claude-skillsBreak a plan, spec, grilling summary or conversation into a set of tracer-bullet tickets — thin, end-to-end slices that each work and can be demonstrated on their own — with explicit "blocked by" edges, so the work forms a dependency graph and anyone can pick up a ticket whose blockers are done. Covers vertical vs horizontal slicing (Hunt & Thomas's tracer bullets, Cockburn's Elephant Carpaccio, INVEST), prefactoring first ("make the change easy, then make the easy change"), sequencing a wide refactor as expand-migrate-contract (Parallel Change), sizing a ticket to one session and one pull req5
- 928Unit Testing Principlesvnovakovits/claude-skillsApply Vladimir Khorikov's unit testing framework from "Unit Testing Principles, Practices, and Patterns" (Manning, 2020). Covers the four pillars (protection against regressions, resistance to refactoring, fast feedback, maintainability) and their unavoidable trade-offs, the three styles of unit testing (output-based, state-based, communication-based), observable behavior vs implementation details as the line that separates good and bad tests, mocks vs stubs with strict verification rules, the managed vs unmanaged dependency distinction (the most useful heuristic for deciding what to mock), wh5
- 929Verification Before CompletionFreddy-CHEN-ux/00_claude_skillsUse when finishing any task. Final checklist before marking complete. Ensures nothing forgotten, all tests pass, documentation updated.8
- 930Voice E2E TestFreddy-CHEN-ux/00_claude_skillsComprehensive E2E test of voice call pipeline - place call, verify auth flow, monitor transcripts/scores, verify report. Use when user says "test voice e2e", "run voice test", or "full voice test".8
- 931Xunit Test Patternsvnovakovits/claude-skillsApply Gerard Meszaros's "xUnit Test Patterns — Refactoring Test Code" (2007) — the canonical catalogue of test-automation patterns, the test-double taxonomy (Dummy, Stub, Spy, Mock, Fake), test smells, fixture strategies, and result-verification patterns. Use when writing or refactoring test code; diagnosing brittle, slow, erratic, or obscure tests; choosing and naming a test double; designing fixtures (fresh vs shared, Object Mother, Test Data Builder, setup styles); structuring the four-phase test; deciding where to draw the test boundary (subcutaneous / layer / round-trip); faking out-of-pr5
- 932Data Result Validationeshmith7/claude-skills-libraryAn honest read on whether a change, test or campaign actually worked, covering effect size, sample adequacy and the traps. Use for A/B tests, before and after comparisons or pilots.5
- 933Edu Assessment Analysiseshmith7/claude-skills-libraryTurn a question-wise mark sheet into item statistics, topic and cognitive-level gaps, groups by what students missed, and a triaged reteach plan. Use for test analysis.5
- 934Never Againmalaysherasia-ai/claude-never-againCapture a bug or mistake as a permanent guardrail so it cannot happen twice. Use this skill whenever a bug is fixed, a test fails and is repaired, the user says "you did that again", "don't do that", "remember this", "never do X", or any correction is made that a future session would otherwise forget. Also use when the user asks to review, promote, or clean up existing lessons and hooks.1
- 935CI Health Reportnpow/claude-skillsUse when checking CI/CD health, Jenkins build failures, flaky tests, build success rates, or generating a CI health report. Trigger phrases: CI health, build failures, jenkins report, flaky tests, build health, are builds passing, CI status.5
- 936Deep QAnpow/claude-skillsUse when reviewing, auditing, QAing, critiquing, verifying, or assessing any artifact — a spec, code change, diff, PR, research report, skill, prompt, or document. Also use for pre-completion verification ("verify this works", "prove this is done", "evidence before claiming complete"). Trigger phrases include "review this", "audit this", "QA this", "find issues", "find defects", "critique this", "check this for problems", "what's wrong with this", "evaluate this", "run QA", "review the diff", "review the PR", "review my code", "deep QA", "defect audit", "code review", "assess this", "verify th5
- 937Deep QA Ensemble V1npow/claude-skillsUse when the user asks to review with ensemble judges, or explicitly requests the ensemble variant of deep-qa. Benchmark variant that uses three heterogeneous providers for severity judging instead of a single judge. Same triggers as deep-qa but with multi-provider ensemble scoring.5
- 938Flaky Test Diagnosernpow/claude-skillsSystematically diagnoses why a test is flaky by running multi-run experiments, isolation tests, ordering permutations, and timing analysis. Use when the user says a test is flaky, intermittent, non-deterministic, randomly failing, passes sometimes, or asks to debug test flakiness.5
- 939Gen Crash Testnpow/claude-skillsCrash-recovery test for the sagaflow generic interpreter. Multiple sequential tool calls with a sleep in the middle.5
- 940Gen Smokenpow/claude-skillsSmoke test for the sagaflow generic interpreter. Writes a greeting to report.md and ends turn. Use only for testing the interpreter round-trip.5
- 941Migrate to ShoehornGAGAA-HUE/ASHUO-claude-skillsMigrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.5
- 942QAGAGAA-HUE/ASHUO-claude-skillsInteractive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".5
- 943Unit Testmoveju112/skill_verifyUse when the user directly requests efficiency-aware multi-angle unit tests or a test report after code changes. Triggers include "단위 테스트", "유닛테스트", "테스트 돌려", "다방면 테스트", "테스트 문서 정리", and the English equivalents "unit test", "run the tests", "multi-angle tests", "write up the test results", and "/unit-test". Codex or Claude runs tests locally without calling another LLM, avoids duplicate full-suite gates, and writes a focused report to the project's test directory. Not for E2E, external DB/network checks, runtime verification, or performance benchmarks.1
- 944Audit Feature GatesTalonT-Org/AutoSkillitAudit feature flag isolation — traces import chains, runtime gates, tool/skill tag coverage, UI surfaces, and test markers to detect leakage and miswiring.5
- 945Audit TestsTalonT-Org/AutoSkillitAudit the test suite for useless tests, consolidation opportunities, over-mocking, weak assertions, placement/organization issues, xdist safety violations, test path filter integrity, and other test quality issues. Use when user says "audit tests", "audit test suite", "review tests", or "test quality check". Generates an improvement plan in temp/ with explanations for each proposed change.5
- 946Design GuardsTalonT-Org/AutoSkillitInvestigate a bug pattern audit report and design architectural guards (tests, contracts, structural changes) that provide immunity to each identified pattern. Use when user says "design guards", "design defenses", or wants architectural solutions for bug patterns.5
- 947Exp Lens Benchmark RepresentativenessTalonT-Org/AutoSkillitCreate Benchmark Representativeness experimental design diagram showing coverage matrix, generalization gaps, and untested regions. Generalizability lens answering "Does this generalize beyond the test bed?5
- 948Exp Lens Exploratory ConfirmatoryTalonT-Org/AutoSkillitAssess whether analytic decisions were pre-specified or post-hoc and whether exploratory/confirmatory norms are aligned. Boundary lens answering "Is this discovery or test, and are norms aligned?5
- 949Exp Lens Severity TestingTalonT-Org/AutoSkillitAnalyze severity of experimental tests — adversarial cases, negative controls, falsification tests, easy-pass detection, and confirmatory theater. Falsificationist lens answering "Would this design have caught the error?5
- 950Resolve FailuresTalonT-Org/AutoSkillitFailure resolution executor. ALWAYS invoke this skill when instructed to fix test failures in a worktree. Do not read test output or edit code directly — use this skill first to load the failure resolution workflow.5
- 951Review PromotionTalonT-Org/AutoSkillitReviewer-facing deep analysis of an integration-to-main promotion. Performs domain risk scoring, breaking change audit, regression risk assessment, test coverage delta, and cross-domain dependency analysis. Use when you want a reviewer's guide before approving a promotion PR.5
- 952Validate AuditTalonT-Org/AutoSkillitValidate audit findings from audit-arch, audit-tests, or audit-cohesion against actual code, git history, and design intent using 9–10 parallel subagents. Removes contested findings, documents exceptions, adjusts severities. Use when user says "validate audit", "validate findings", "validate report", or "check audit results".5
- 953Validate AuditTalonT-Org/AutoSkillitValidate audit findings from audit-arch, audit-tests, audit-cohesion, audit-feature-gates, audit-docs, or audit-review-decisions against actual code, git history, and design intent using 9–10 parallel subagents. Removes contested findings, documents exceptions, adjusts severities. Use when user says "validate audit", "validate findings", "validate report", or "check audit results".5
- 954Validate Review DecisionsTalonT-Org/AutoSkillitValidate review-decisions audit findings with mandatory intent analysis and seven evidence-gathering rules. Adds docstring-as-contract recognition, deliberate-change detection, test-as-intent-signal, consumer-impact verification, architectural feasibility checks, behavioral simulation, and symmetry-as-design recognition to the standard validation workflow. Use when validating reports from audit-review-decisions specifically.5
- 955Validate Test AuditTalonT-Org/AutoSkillitValidate test audit findings with test-domain semantic rules and intent analysis. Adds import-path-as-contract recognition, precondition-as-assertion detection, provenance verification, split-era lifecycle awareness, and deletion-vs-improvement distinction to the standard validation workflow. Use when validating reports from audit-tests specifically.5
- 956Webapp Testinganthropics/skillsToolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
- 957Test Reviewpriyank766/OpenSource-SKILLReview of test quality in an open-source pull request, and of the tests the PR should have written but did not. Use when the diff is mostly under tests/ or spec/, when new test files or test helpers are added, when fixtures, factories, mocks or golden/snapshot files change, when CI is flaky or intermittently red, or when judging whether a behaviour change in the PR is actually covered by anything that would fail if the behaviour regressed. Applies the suite's weighted 10-point filter at a floor of 8.0 and judges every test by one question — would it fail if the implementation broke? Language- 1
- 958Azure Resource Manager Playwright Dotnetlucaspmarie-a11y/claude-skills-vaultAzure Resource Manager SDK for Microsoft Playwright Testing in .NET.5
- 959Bash Scriptinglucaspmarie-a11y/claude-skills-vaultBash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing.5
- 960Burp Suite Testinglucaspmarie-a11y/claude-skills-vaultExecute comprehensive web application security testing using Burp Suite's integrated toolset, including HTTP traffic interception and modification, request analysis and replay, automated vulnerability scanning, and manual testing workflows.5