Skip to content

Explore skills

Search every indexed skill by name, description, repository or instructions, then narrow the results.

Showing 25471–25500 of 29853 skills

auditing-accessibilityjaktestowac/awesome-copilot-for-testersPerforms webpage and user-flow accessibility audits with WCAG 2.2 guidance, manual verification checklists, prioritized remediation output, and stakeholder-ready summaries. Use when auditing accessibility on a URL, triaging suspected a11y issues, or producing technical findings with practical next steps.Stars: 122Updated Claude CodeCodexUnverifiedInstall
code-review-advancedjaktestowac/awesome-copilot-for-testersPerforms evidence-driven code review for pull requests, legacy modules, and quality-critical changes. Use when reviewing complex or multi-file changes, test automation suites, architectural refactors, or hot paths that need analysis of correctness, maintainability, security, performance, test quality, and operability risks. Provides structured feedback with severity-ranked findings, actionable recommendations, and clear rationale. For a fast sanity check of a small diff or single file, use the code-review skill instead.Stars: 122Updated Claude CodeCodexUnverifiedInstall
code-reviewjaktestowac/awesome-copilot-for-testersPerforms a quick, lightweight review of a small diff or single file, giving concise feedback on correctness, readability, tests, and obvious risks. Use when the user asks for a fast sanity-check review of a small change. For test-automation suites, architectural refactors, security-sensitive paths, or multi-file reviews, use the code-review-advanced skill instead.Stars: 122Updated Claude CodeCodexUnverifiedInstall
communicating-quality-findingsjaktestowac/awesome-copilot-for-testersShapes QA output for the person who has to act on it: result and blocker in the first two lines, one decision per report, findings ordered by what they cost, the long artifact in a file and the decisions in the message, and magnitude stated in units the reader can count. Use when a report is accurate but nobody acts on it, when a finding set is too long to read under time pressure, when the same findings must be retold for a developer, a release manager, and an on-call engineer, or when the request mentions "too long", "make this readable", "just tell me what to do", "so what", or "summarize this for stakeholders". Pairs with unslop-answers, which makes the same report honest.Stars: 122Updated Claude CodeCodexUnverifiedInstall
creating-custom-agentsjaktestowac/awesome-copilot-for-testersCreates GitHub Copilot custom agents (`.agent.md`) for VS Code. Use when defining a specialized agent role, selecting a minimal toolset, referencing supporting skills, or shipping install-ready agent examples with clear boundaries and collaboration rules.Stars: 122Updated Claude CodeCodexUnverifiedInstall
creating-hooksjaktestowac/awesome-copilot-for-testersCreates GitHub Copilot hooks for VS Code using `hooks.json`, supporting scripts, and companion docs. Use when automating deterministic checks, pre/post tool policies, or reusable hook packs that need safe defaults, observability, and clear installation guidance.Stars: 122Updated Claude CodeCodexUnverifiedInstall
creating-instructionsjaktestowac/awesome-copilot-for-testersCreates GitHub Copilot instruction files for VS Code, including repository guidance and scoped `.instructions.md` rules. Use when encoding project conventions, choosing `applyTo` patterns, or shipping install-ready instruction examples with rationale and guardrails.Stars: 122Updated Claude CodeCodexUnverifiedInstall
creating-orchestration-packsjaktestowac/awesome-copilot-for-testersCreates agent orchestration packs: cooperating `.agent.md` files with an orchestrator, subagents, matched handoffs, minimal tool grants, and a shared handoff packet contract. Use when one agent role is too broad for a job, when a workflow needs explore, plan, implement, review, and verify as separate roles, or when a pack fails the orchestration lint because a handoff target does not resolve.Stars: 122Updated Claude CodeCodexUnverifiedInstall
creating-pluginsjaktestowac/awesome-copilot-for-testersPackages repository skills as installable Copilot plugins: marketplace registration, `plugin.json` manifests, generated skill copies, and the sync check CI enforces. Use when bundling one or more skills for installation, when adding a plugin to the marketplace, or when `npm run lint` reports that a plugin copy has drifted from its source skill.Stars: 122Updated Claude CodeCodexUnverifiedInstall
creating-promptsjaktestowac/awesome-copilot-for-testersCreates GitHub Copilot prompt files (`.prompt.md`) for VS Code. Use when building reusable workflow starters that route work to the right agent, collect the right inputs, and ship with install-ready templates, examples, and validation guidance.Stars: 122Updated Claude CodeCodexUnverifiedInstall
creating-skillsjaktestowac/awesome-copilot-for-testersCreates GitHub Copilot skills with reusable workflows, companion resources, and validation gates. Use when packaging repeatable expertise into a `SKILL.md` folder, deciding what belongs in the skill body versus resources, or producing install-ready skill examples for a team or collection.Stars: 122Updated Claude CodeCodexUnverifiedInstall
deriving-a-quality-contractjaktestowac/awesome-copilot-for-testersDerives a project-specific quality contract from three axes - risk profile, team maturity, and product surface - labelling each testing practice MUST, SHOULD, or COULD, then produces a PRESENT/PARTIAL/MISSING/WAIVED gap matrix with an ordered remediation plan. Use when a project has no agreed testing strategy, when a team argues about which practices are mandatory, when onboarding a legacy or inherited repository, when a quality strategy document has to be derived from evidence instead of opinion, or when someone asks "what testing should we actually be doing here".Stars: 122Updated Claude CodeCodexUnverifiedInstall
designing-functional-testsjaktestowac/awesome-copilot-for-testersDesigns risk-based functional test plans, manual test cases, regression slices, and automation handoff packs from requirements, URLs, or exploratory notes. Use when preparing manual QA coverage before automation, turning feature descriptions into scenario catalogs, or converting exploratory findings into structured test assets.Stars: 122Updated Claude CodeCodexUnverifiedInstall
designing-test-datajaktestowac/awesome-copilot-for-testersDesigns realistic, boundary-heavy, and role-aware test data packs for manual and automated testing. Use when a feature needs deliberate inputs and fixtures before execution, when edge-case values keep being improvised, or when automation needs stable example data with setup notes.Stars: 122Updated Claude CodeCodexUnverifiedInstall
documenting-test-suitesjaktestowac/awesome-copilot-for-testersWrites the documentation a test suite needs to be usable by someone who did not build it: run instructions, environment setup, tag glossary, ownership, fixture and data notes, and architecture decision records. Use when onboarding someone into a suite, when "how do I run these" keeps being asked, when a test architecture decision needs recording, or when a suite is inherited with no documentation.Stars: 122Updated Claude CodeCodexUnverifiedInstall
generating-quality-gate-workflowsjaktestowac/awesome-copilot-for-testersGenerates the CI workflow that enforces a quality contract: layered jobs from fast local hooks to release gates, per-practice steps for JS/TS toolchains, diff-scoped checks, sticky PR reporting, required-check wiring, and a severity policy deciding what fails the build. Use when quality practices are agreed but not enforced, when CI runs everything on every commit, when a gate reports green while the check it runs cannot fail, or when a per-change gate needs to post findings on the pull request.Stars: 122Updated Claude CodeCodexUnverifiedInstall
governing-quality-waiversjaktestowac/awesome-copilot-for-testersTurns "we will skip this check for now" into a dated, attributed, expiring waiver with a stated reason and owner, inventories the silent skips already hiding in a repo - skipped tests, disabled lint rules, ts-expect-error, continue-on-error, lowered thresholds, coverage ignores - and reports expired waivers as findings. Use when a team wants to bypass a quality gate, when skip lists and quarantined tests accumulate without owners, when an audit asks why a check is off, or when a repo needs to know what it has quietly stopped enforcing.Stars: 122Updated Claude CodeCodexUnverifiedInstall
handling-sensitive-test-datajaktestowac/awesome-copilot-for-testersKeeps test data legally and operationally safe: classifies personal data, replaces production copies with synthetic or anonymized fixtures, manages secrets in local runs and CI, strips personal data from traces and HAR files, and sets retention rules. Use when tests run against a production data copy, when fixtures contain real names or emails, when a data protection review is coming, or when test artifacts might carry personal data into CI logs.Stars: 122Updated Claude CodeCodexUnverifiedInstall
migrating-tests-to-playwrightjaktestowac/awesome-copilot-for-testersMigrates Cypress, Selenium, WebdriverIO, or Protractor suites to Playwright in staged slices, each with a parity gate before the old test is deleted. Use when porting a legacy browser suite, when deciding which tests are not worth porting, when a half-finished migration has stalled with two suites running in parallel, or when a suite migration needs a plan before anyone starts translating files.Stars: 122Updated Claude CodeCodexUnverifiedInstall
mocking-network-and-timejaktestowac/awesome-copilot-for-testersDecides what to fake and stubs it correctly: network interception with Playwright route or HAR replay, MSW handlers, fake clocks, and fixed timezones. Use when a test depends on a third party, when a date-sensitive test breaks overnight, when a suite is slow because it calls real services, or when a mocked test stays green while production is broken.Stars: 122Updated Claude CodeCodexUnverifiedInstall
planning-exploratory-testingjaktestowac/awesome-copilot-for-testersRuns session-based exploratory testing: writes charters, timeboxes sessions, applies coverage heuristics and tours, captures notes as evidence, debriefs, and converts findings into bug reports and automation candidates. Use when a feature needs testing before requirements settle, when scripted cases keep passing while users hit problems, when a release needs a risk sweep with limited time, or when the request mentions charters or exploratory sessions.Stars: 122Updated Claude CodeCodexUnverifiedInstall
prd-generatorjaktestowac/awesome-copilot-for-testersProduces production-ready Product Requirements Documents (PRDs) for software systems and AI-powered features, with clear problem framing, measurable outcomes, scoped functionality, testable requirements, and explicit risks. Use when the user wants to write a PRD, define requirements, plan a feature, or turn a vague product idea into an implementation-ready specification.Stars: 122Updated Claude CodeCodexUnverifiedInstall
recording-change-intentjaktestowac/awesome-copilot-for-testersRequires an externalised rationale for high-risk changes - new public exports, new endpoints, auth edits, migrations, removed guards - recorded as an Intent commit trailer, an ADR reference, or a module intent register, and reports high-risk changes that carry none. Use when agent-generated or AI-assisted changes ship without a recorded why, when reviewers cannot tell what a diff was for, when a codebase is losing its decision history, or when setting up an intent gate alongside test and coverage gates.Stars: 122Updated Claude CodeCodexUnverifiedInstall
reporting-bugsjaktestowac/awesome-copilot-for-testersTransforms rough tester notes, screenshots, console output, or observed behavior into reproducible defect reports with severity, evidence, and follow-up guidance. Use when logging bugs, triaging intermittent issues, or rewriting vague defect notes into developer-ready reports.Stars: 122Updated Claude CodeCodexUnverifiedInstall
requirements-test-coverage-mapperjaktestowac/awesome-copilot-for-testersMaps requirements (PRD, user stories, acceptance criteria) to planned test coverage via a Requirements Traceability Matrix, exposing coverage gaps, risks, test levels, prioritization, and automation candidates. Use when designing coverage from a specification, checking coverage completeness for a PRD or user story, finding missing acceptance criteria, or building a risk-based regression strategy. When the tests already exist and the matrix has to be extracted from them, verified, and kept accurate, use the tracing-requirements-to-code skill instead.Stars: 122Updated Claude CodeCodexUnverifiedInstall
reviewing-ai-output-groundednessjaktestowac/awesome-copilot-for-testersHuman review protocol for whether AI output is grounded in its sources: claim-by-claim attribution, hallucination classes, citation verification, sampling that is defensible, and a recorded attestation because groundedness cannot be fully automated. Also covers the responsible-AI pass - harmful output, bias, disclosure and privacy. Use when reviewing a RAG or summarisation feature, when factuality matters more than fluency, or when an eval suite needs the human check it cannot replace.Stars: 122Updated Claude CodeCodexUnverifiedInstall
running-visual-regression-testsjaktestowac/awesome-copilot-for-testersSets up and maintains visual regression testing: what to snapshot, baseline strategy, masking dynamic regions, threshold tuning, containerized baselines, and the review-and-update workflow. Use when styling regressions escape to production, when snapshots fail on every machine or every run, when baselines are being updated without being looked at, or when deciding whether visual testing is the right tool at all.Stars: 122Updated Claude CodeCodexUnverifiedInstall
scoping-change-relevancejaktestowac/awesome-copilot-for-testersClassifies a diff into file tags and hunk tags - new public export, new endpoint, modified auth, SQL string, migration, added dependency, touched prompt - then maps each tag to the quality practices it makes relevant, producing a defensible per-change check scope instead of running everything or guessing. Use when deciding what to test for a specific pull request, when a full regression run is too slow to gate on, when a pre-push or PR gate needs a scope someone can argue with, or when asked "which checks does this change actually need".Stars: 122Updated Claude CodeCodexUnverifiedInstall
static-code-analysis-typescriptjaktestowac/awesome-copilot-for-testersCreates, reviews, and modernizes static code analysis setups for Node.js and TypeScript repositories, covering ESLint flat config, typescript-eslint, tsconfig, Prettier, import sorting, Husky, lint-staged, package.json quality scripts, and CI quality gates. Use when setting up or auditing linting, formatting, type-checking, commit hooks, or GitHub Actions quality checks in a TypeScript project.Stars: 122Updated Claude CodeCodexUnverifiedInstall
tech-debt-analysisjaktestowac/awesome-copilot-for-testersAnalyzes technical debt in codebases, test suites, architecture, dependencies, and delivery workflows using observable signals. Use when auditing repository health, explaining slow delivery or flaky tests, prioritizing refactoring, or building an evidence-based remediation roadmap with risk, effort, and ROI. Use when user asks for technical debt analysis, repository audit, or refactor planning.Stars: 122Updated Claude CodeCodexUnverifiedInstall