Saltar al contenido
Tienda

Pruebas y calidad

Skills para escribir pruebas, revisar cambios, cazar bugs y mantener el código sano.

1074 skills

Las más instaladas primero

  1. tddmattpocockTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.1 M instalaciones en skills.sh1
  2. diagnosing-bugsmattpocockDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.728.5 k instalaciones en skills.sh0
  3. code-reviewmattpocockReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".678.9 k instalaciones en skills.sh0
  4. minimal-run-and-auditlllllllamaRigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.450.2 k instalaciones en skills.sh0
  5. setup-pre-commitmattpocockSet up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.426.4 k instalaciones en skills.sh0
  6. scaffold-exercisesmattpocockCreate exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.418.6 k instalaciones en skills.sh0
  7. prisma-upgrade-v7prismaOficialComplete migration guide from Prisma ORM v6 to v7 covering all breaking changes. Use when upgrading Prisma versions, encountering v7 errors, or migrating existing projects. Triggers on "upgrade to prisma 7", "prisma 7 migration", "prisma-client generator", "driver adapter required".327.8 k instalaciones en skills.sh0
  8. analyze-projectlllllllamaRigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrypoints, review configs and insertion points, or flag suspicious implementation patterns without modifying code or running heavy jobs. Do not use for active command execution, broad refactoring, speculative code adaptation, or automatic bug fixing.311.2 k instalaciones en skills.sh0
  9. safe-debuglllllllamaRigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.310.7 k instalaciones en skills.sh0
  10. explore-runlllllllamaRigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subset validation, short-cycle guess-and-check, batch sweeps, idle-GPU search, or quick transfer-learning trials, with fair-comparison caveats and no-overclaim summaries in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline execution, conservative training verification, default routing, verified SOTA claims, or implicit experimentation.310.5 k instalaciones en skills.sh0
  11. systematic-debuggingobraUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes280.9 k instalaciones en skills.sh0
  12. requesting-code-reviewobraUse when completing tasks, implementing major features, or before merging to verify work meets requirements243.6 k instalaciones en skills.sh0
  13. test-driven-developmentobraUse when implementing any feature or bugfix, before writing implementation code242.6 k instalaciones en skills.sh0
  14. verification-before-completionobraUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always228.9 k instalaciones en skills.sh0
  15. seo-auditcoreyhaines31When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.221.3 k instalaciones en skills.sh0
  16. receiving-code-reviewobraUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation206.9 k instalaciones en skills.sh0
  17. playwright-climicrosoftOficialAutomate browser interactions, test web pages and work with Playwright tests.176.5 k instalaciones en skills.sh0
  18. webapp-testinganthropicsOficialToolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.171 k instalaciones en skills.sh0
  19. workers-best-practicescloudflareOficialCloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.102.2 k instalaciones en skills.sh0
  20. firecrawlfirecrawlOficialAny live-web task via the Firecrawl CLI — including ordinary web research: searching the web, reading or extracting pages, gathering sources, discovering site URLs, bulk extraction, downloading a site, change alerts, or pages needing clicks/login — web only; local files route to firecrawl-parse. For papers use firecrawl-research-index; for library, API, error, or bug questions use firecrawl-developer-index.101.8 k instalaciones en skills.sh0
  21. web-perfcloudflareOficialAudit, diagnose, or optimize website loading and interaction performance, Core Web Vitals, and Lighthouse performance scores.91.9 k instalaciones en skills.sh0
  22. review-loop2dmuraliIterative worker-reviewer cycle that spawns a critic subagent to score work 1-10 and provide actionable feedback, then revises until a quality gate is met. Use when implementing features, writing specs, reviewing existing code, or completing any task where quality matters more than speed. Trigger phrases: "use review-loop", "polish this", "iterate on this", "/review-loop", "review with feedback loop".90.9 k instalaciones en skills.sh0
  23. playwright-best-practicescurrents-devUse when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.90.4 k instalaciones en skills.sh0
  24. safe-refactorjuliusbrusseeRestructure code while preserving behavior. Use for extraction, consolidation, ownership moves, or cleanup where verification must bracket structural edits.86.5 k instalaciones en skills.sh0
  25. investigate-firstjuliusbrusseeDiagnose ambiguous failures before editing. Use for unknown causes, intermittent behavior, performance regressions, or investigations needing evidence-ranked hypotheses.85.5 k instalaciones en skills.sh0
  26. verify-and-stopjuliusbrusseeProve existing work meets acceptance conditions without expanding scope. Use for validation-only tasks, completion checks, focused gate runs, and last-mile proof.85.2 k instalaciones en skills.sh0
  27. surgical-patchjuliusbrusseeFix bugs and small behavior changes at the narrowest responsible layer. Use when regression proof, preserved surrounding behavior, and task-relevant tests matter.85.1 k instalaciones en skills.sh0
  28. competitor-profilingcoreyhaines31When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.84.6 k instalaciones en skills.sh0
  29. solana-devsolana-foundationUse when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "fuzz my Solana program", "deploy to devnet", "send a v1 transaction", "support larger transactions", "fix maxSupportedTransactionVersion", or "explain Solana concepts" (rent, accounts, PDAs, CPIs). Also for program architecture — state layout, reducing compute units, throughput bottlenecks, instruction naming — and quick on-chain lookups via public RPC + curl (balance, transaction, token account). End-to-end playbook: wallet connection, Anchor/Pinocchio programs, Codama clients, Surfpool/LiteSVM/Mollusk testing, security review, and the v1 transaction format (SIMD-0385, 4096-byte transactions). Prefers @solana/kit 8 plugin clients (createClient + .use()) building transaction v1 by default, @solana/kit-plugin-wallet + @solana/react for wallets, web3.js v3 (RC) as the legacy migration target, and Surfpool for local networks.83.3 k instalaciones en skills.sh0
  30. auditpbakausa user-authored audit skill81.9 k instalaciones en skills.sh0

Otras categorías

Deska lista estas skills; las escribieron sus autores. Una skill corre con los permisos de tu agente, así que lee lo que hace antes de instalarla.

¿Falta una skill? Sugiere su repositorio desde tu cuenta y el equipo de Deska la agregará. Sugerir un repositorio