All categories
Testing & QA
Unit tests, integration tests, E2E, QA, validation, and test automation
- 29,816
- 1,243
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse testing & qa skills
Showing 961–984 of 29,816 skills
- TddUse before implementing features or bug fixes with testable behavior, including requests that do not mention tests or TDD. Not for behavior-preserving refactors or prose, styling, and static-content edits.Votes: 0GitHub stars: 3
- Simplify Code SolutionSimplify a proposed or existing code solution through recommendations or implementation while preserving requirements and clear ownership.Votes: 0GitHub stars: 3
- Diagnosing BugsReproduce, isolate, and fix difficult bugs or performance regressions.Votes: 0GitHub stars: 3
- Test Impact And ConsolidationMeasure which test files carry the least evidence and decide which may be merged or removed. Use when the suite has grown, when a run is slow, when asked which tests matter, or before adding a test that may already exist. Ranks by marginal coverage, then adjudicates each shortlisted file by planting faults.Votes: 0GitHub stars: 57
- Test AuditInvoke whenever writing, changing, reviewing, or sweeping tests in Anabasis. A write-time gate for every new or changed test, and a read-first audit that prunes or consolidates tests re-asserting source, duplicating a stronger owner, coupling to implementation, or keeping a test-only export alive. Knows the suite's helpers, fakes, walls, rule-4 invariance tests and runner, and hands removal claims that rest on overlap to test-impact-and-consolidation.Votes: 0GitHub stars: 57
- Spark Create ComponentCreate a new component in the Modules folder from template with proper documentation and placeholders replacement.Votes: 0GitHub stars: 22
- Spark Component View ModelCreate or update an view model file in the ViewModel folder in Sources of a spark-ios-component-XXX and add or update unit tests.Votes: 0GitHub stars: 22
- Spark Component Snapshots TestingCreate or update the snapshots testing for a spark-ios-component-XXX.Votes: 0GitHub stars: 22
- Spark Component EnvironmentCreate or update an environment file in the Environment folder in Sources of a spark-ios-component-XXX and add or update unit tests.Votes: 0GitHub stars: 22
- Spark Component ConstantsCreate or update a constants file in the Constants folder in Sources of a spark-ios-component-XXX and add or update unit tests.Votes: 0GitHub stars: 22
- Spark Component Accessibility IdentifierCreate or update a accessibility identifier file in the AccessibilityIdentifier folder in Sources of a spark-ios-component-XXX and add or update unit tests.Votes: 0GitHub stars: 22
- TestRun the full test suite AND expand coverage for the current change — the dedicated testing pass. Its ONLY job is tests. Use after implementing or verifying a change, and whenever the user says "test", "run tests", "cover this", "write tests", or "make sure it's tested". Enforces: nothing is done until the suite is green and every change is covered (with a regression test per bug fixed).Votes: 0GitHub stars: 2
- Plan GatesThe full plan → gate → commit procedure for full-gear work: new features, multi-file refactors, schema/API changes, anything security-sensitive or where the approach is genuinely uncertain. Use whenever a task warrants the "full" gear from the global gears table, or when the user says "plan this", "full workflow", or asks for the adversarial planning panel. Covers Phase 1 (orient, draft, adversarial critics, plan file, approval stop) and Phase 2 (implement on mid-tier agents, five gates — con...Votes: 0GitHub stars: 2
- Parent SyncSync web-ui with a newer parent career-ops release — pull the parent, scope the delta, port providers/fixes, fan out docs ×17, run every gate, ship the parity release end-to-end. Trigger when the user says "обнови родителя", "parent-sync", "возьми новое из родителя", or pastes a santifer/career-ops release URL.Votes: 0GitHub stars: 79
- Playwright InteractivePersistent browser and Electron interaction through `js_repl` for fast iterative UI debugging.Votes: 0GitHub stars: 27,803
- Define GoalHelp the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.Votes: 0GitHub stars: 27,803
- Vector ForgeMutation-driven test vector generation. Finds implementations of a cryptographic algorithm or protocol, runs mutation testing to identify escaped mutants, then generates new test vectors that deliberately exercise the uncovered code paths. Compares before/after mutation kill rates to prove vector effectiveness. Use when generating cryptographic test vectors, measuring Wycheproof coverage gaps, finding escaped mutants via mutation testing, creating cross-implementation test suites, or improvin...Votes: 0GitHub stars: 7,287
- GenotoxicGraph-informed mutation testing triage. Parses codebases with Trailmark, runs mutation testing and necessist, then uses survived mutants, unnecessary test statements, and call graph data to identify false positives, missing test coverage, and fuzzing targets. Use when triaging survived mutants, analyzing mutation testing results, identifying test gaps, finding fuzzing targets from weak tests, running mutation frameworks (including circomvent and cairo-mutants), or using necessist.Votes: 0GitHub stars: 7,287
- WycheproofValidates cryptographic implementations against Project Wycheproof's test vectors, which encode known attacks and edge cases across AES, RSA, ECDSA, ECDH, and more. Covers loading test vectors, mapping result flags onto pass and fail expectations, and reading a failure. Use when testing a crypto implementation against known attacks, checking a library against standard test vectors, or investigating why two implementations disagree on the same input.Votes: 0GitHub stars: 7,287
- RuzzySets up and runs Ruzzy, Trail of Bits' coverage-guided Ruby fuzzer and the only production-ready one for the language. Covers harness structure, fuzzing pure Ruby and the native C extensions in gems, and sanitizer builds. Use when fuzzing a Ruby library or gem, testing a Ruby C extension for memory safety, or asking how to fuzz Ruby at all.Votes: 0GitHub stars: 7,287
- Fuzzing ObstaclesPatches past the barriers that stop a fuzzer making progress — checksum and hash verification, magic-value validation, time-based seeds, and other non-deterministic global state. Covers locating the blocking check, neutering it behind a fuzzing build flag, and avoiding the false positives a patch can introduce. Use when a fuzzer is stuck at validation, when coverage shows large regions behind a checksum, or when valid inputs are impractical to generate.Votes: 0GitHub stars: 7,287
- AtherisSets up and runs Atheris, the coverage-guided Python fuzzer built on libFuzzer. Covers TestOneInput harnesses, FuzzedDataProvider, instrumenting both pure Python and native C extensions, and running under AddressSanitizer. Use when fuzzing a Python package, hunting memory corruption in a Python C extension, or choosing between Atheris and Hypothesis for a Python target.Votes: 0GitHub stars: 7,287
- Semgrep Rule CreatorCreates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Use when writing Semgrep rules or building custom static analysis detections.Votes: 0GitHub stars: 7,287
- Ton Vulnerability ScannerScans TON (The Open Network) smart contracts for 3 critical vulnerabilities including integer-as-boolean misuse, fake Jetton contracts, and forward TON without gas checks. Use when auditing FunC contracts.Votes: 0GitHub stars: 7,287