All categories
Testing & QA
Unit tests, integration tests, E2E, QA, validation, and test automation
- 31,457
- 1,311
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 4,417–4,440 of 31,457 skills
- Python DebugDebug Python code using tracebacks, pdb, and structured logging.Votes: 0GitHub stars: 5
- PublicWrite and run tests for bash scripts with bashunit. Use when adding or fixing tests for shell code, when a bashunit run fails, or when asked to raise coverage of a bash script. Covers loading the code under test, the assertion catalogue, the fast edit-run loop, and the API traps that produce silently-passing tests.Votes: 0GitHub stars: 434
- Tdd CycleRun complete TDD red-green-refactor cycle for a testVotes: 0GitHub stars: 434
- ReviewReview a GitHub pull request; defaults to the current branch's PR when no number is givenVotes: 0GitHub stars: 434
- ReleaseRun pre-release validation and execute the release processVotes: 0GitHub stars: 434
- Pre ReleaseRun comprehensive pre-release validation checklistVotes: 0GitHub stars: 434
- PrPush branch and create a GitHub PR with concise, issue-linked descriptionVotes: 0GitHub stars: 434
- Gh IssuesWalk over all open GitHub issues that are unassigned or assigned to the current user, and process each one via the /gh-issue skill, sequentially.Votes: 0GitHub stars: 434
- Gh IssueFetch GitHub issue, create branch, plan and implement with TDD, then open PRVotes: 0GitHub stars: 434
- Fix TestDebug and fix failing tests systematicallyVotes: 0GitHub stars: 434
- CommitStage and commit changes using conventional commits formatVotes: 0GitHub stars: 434
- Check CoverageAnalyze test coverage and identify untested code pathsVotes: 0GitHub stars: 434
- Add AssertionAdd new assertion function with comprehensive tests following TDDVotes: 0GitHub stars: 434
- Rust EngineerWrites, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo,...Votes: 0GitHub stars: 20
- PrCreate pull requests with structured descriptionVotes: 0GitHub stars: 20
- Lint FixDetect project linting and validation tools, build an execution pipeline, run all tools to zero errors, and fix issues using an atomic fix protocol. Auto-detects Makefile targets, package.json scripts, Go tools, Python tools, and other common linters. Use when fixing linting errors, running validation pipelines, or ensuring code quality before committing.Votes: 0GitHub stars: 20
- Csharp DeveloperUse when building C# applications with .NET 8+, ASP.NET Core APIs, or Blazor web apps. Builds REST APIs using minimal or controller-based routing, configures database access with Entity Framework Core, implements async patterns and cancellation, structures applications with CQRS via MediatR, and scaffolds Blazor components with state management. Invoke for C#, .NET, ASP.NET Core, Blazor, Entity Framework, EF Core, Minimal API, MAUI, SignalR.Votes: 0GitHub stars: 20
- ImplementImplements any code change in the ELPS codebase. This is the foundation skill — all other skills reference its patterns.Votes: 0GitHub stars: 36
- Nix For DevUse this when setting up Nix for a development project (devShell + package build) and you care about `nix develop` being fast. Covers the zero-inputs flake.nix + npins + default.nix/shell.nix layout, sub-flakes for non-user-facing Nix, and language-specific recommendations.Votes: 0GitHub stars: 959
- DoDo a task end-to-end — implement, PR, CI loop, ship. ONLY invoke when the user explicitly types `/do` or `$do`; never auto-select from a natural-language request, even one that sounds like an end-to-end task.Votes: 0GitHub stars: 959
- QaUse when implementation is complete and you want to verify quality through adversarial testing that writes code and provides evidenceVotes: 0GitHub stars: 484
- Dot File HoneUse when a pipeline DOT file has passed structural validation but may still have flow inefficiencies, spec fidelity gaps, or information loss in prompts. Use after dotfile-audit or dotfile-from-spec when you want to deeply verify a pipeline captures everything from the original spec. Use when prompts might be missing critical domain rules, data models, or invariants.Votes: 0GitHub stars: 334
- Dot File AuditUse when you have an existing pipeline DOT file that needs review, fixing, or validation. Use when validation produces warnings or errors, when a DOT file was hand-written or generated by another tool, or when you want to verify a pipeline covers 100% of a spec before running it.Votes: 0GitHub stars: 334
- BuildFull build pipeline: takes a PRD, breaks it into tasks, implements them in parallel, and reviews the result. Orchestrates prd-task-planner → parallel-task-orchestrator → code-reviewer.Votes: 0GitHub stars: 31