AI TOOLS RADAR
Tous les Skills / LANGGENIUS
langgenius/dify

frontend-testing

Use when writing or changing Vitest or React Testing Library tests under web/ or packages/dify-ui/, or when the user explicitly requests frontend test strategy, including evaluation of an existing strategy.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/langgenius/dify --skill frontend-testing

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Frontend Testing

Read the testing policy for the package that owns the changed tests:

  • web/: web/docs/test.md owns Web test boundaries, environments, and commands.
  • packages/dify-ui/: packages/dify-ui/docs/testing.md owns primitive test boundaries, environments, Storybook, and commands.

This skill adds no parallel policy or check sequence. Follow the selected owner's requirements, including its validation commands. Recommend deleting low-value tests as readily as adding missing behavior coverage, and report the contract verified and any material verification gap.

Tâches connexes

affaan-m
Communauté

springboot-verification

Run the full Spring Boot verification loop — Maven or Gradle build, SpotBugs, PMD, and Checkstyle static analysis, unit and Testcontainers integration tests with JaCoCo coverage, OWASP dependency and secret scans, and diff review — producing a pass/fail readiness report. Use when preparing a Spring Boot pull request, validating coverage thresholds, or running pre-deploy verification.

installations
3
GitHub Stars
288,1 k
Mis à jour
20 oct.
MIT1 Fichiers
Voir les détails →

Raison de la sélection: Tests et sécurité

affaan-m
Communauté

tdd-workflow

Test-driven development workflow: write a failing test first, watch it fail, implement the smallest change to green, then refactor with 80%+ coverage across unit, integration, and E2E tests. Use when writing a new feature, fixing a bug, refactoring, or when told to write failing tests first.

installations
3
GitHub Stars
287,3 k
Mis à jour
20 oct.
MIT1 Fichiers
Voir les détails →

Raison de la sélection: Tests et sécurité

morluto
Communauté

rea-ci-tests-audit

Audit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.

installations
5
GitHub Stars
345,8 k
Mis à jour
20 oct.
MIT3 Fichiers
Voir les détails →

Raison de la sélection: Tests et sécurité

mattpocock
Communauté

code-review

Review 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\".

installations
792,4 k
GitHub Stars
302,5 k
Mis à jour
22 oct.
MIT2 Fichiers
Voir les détails →

Raison de la sélection: Tests et sécurité

du même dépôt

Autres Skills

Tous les Skills
langgenius
Communauté

frontend-code-review

Use only when the user explicitly requests a review or audit of frontend code under web/ or packages/dify-ui/. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests, diagnosis without review intent, or backend-only code.

installations
1
GitHub Stars
159,1 k
Mis à jour
21 oct.
NOASSERTION9 Fichiers
Voir les détails →