Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

visual-verification

Étoiles18

Forks2

Mis à jour3 janvier 2026 à 19:44

Visually verify implemented features work correctly before marking complete. Use when testing UI changes, verifying web features, or checking user flows work in the browser.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

gruckion

gruckion/marathon-ralph

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

Explorateur de fichiers

3 fichiers

SKILL.md

readonly

name	visual-verification
description	Visually verify implemented features work correctly before marking complete. Use when testing UI changes, verifying web features, or checking user flows work in the browser.

Visual Verification

Verify implemented features work correctly through actual user interaction, not just automated tests.

When to Use

After implementing any UI feature
Before marking an issue as complete
When acceptance criteria involve user-visible behavior
After fixing UI bugs

Approaches

Web Applications: See browser-verification.md for Playwright MCP workflow.

Mobile Applications: See mobile-verification.md (Coming soon)

Verification Checklist

Before marking any UI task complete:

Dev server is running and accessible
Feature renders without console errors
Elements render correctly and do not incorrectly overlap
User interactions work as expected
Edge cases handled (empty states, loading, errors)
Screenshot captured as evidence

What NOT to Do

Skip visual verification because "tests pass"
Mark issues complete without browser testing
Assume dev mode catches all errors (run npm run build too)
Test only happy paths

Plus depuis ce dépôt

même dépôt

update-state

gruckion/marathon-ralph

Programmatically update marathon-ralph state file using deterministic jq commands. Use this instead of manually editing the JSON file.

2026-01-0418

marathon-ralph

gruckion/marathon-ralph

Autonomous long-running development from specifications. Use when user wants to build an application from a spec file, run continuous development, or automate feature implementation. Triggers on phrases like "marathon this", "build from spec", "autonomous development", "keep coding until done".

2026-01-0318

project-detection

gruckion/marathon-ralph

Detects project type, package manager, and monorepo structure. Returns correct commands for test/build/lint/dev. Run at project initialization and cache results in state. Use before running any build/test commands.

2026-01-0318

setup-playwright

gruckion/marathon-ralph

Configure Playwright for E2E testing. Use when setting up end-to-end tests, when no E2E framework is detected, or when the user asks to configure browser testing.

2026-01-0318

setup-vitest

gruckion/marathon-ralph

Configure Vitest for unit and integration testing. Use when setting up a test framework, when no test runner is detected, or when the user asks to configure testing.

2026-01-0318

write-playwright-test

gruckion/marathon-ralph

Write Playwright E2E tests using fixtures and best practices. Use when creating E2E tests, writing browser automation tests, or testing user flows.

2026-01-0318

name	visual-verification
description	Visually verify implemented features work correctly before marking complete. Use when testing UI changes, verifying web features, or checking user flows work in the browser.

Visual Verification

Verify implemented features work correctly through actual user interaction, not just automated tests.

When to Use

After implementing any UI feature
Before marking an issue as complete
When acceptance criteria involve user-visible behavior
After fixing UI bugs

Approaches

Web Applications: See browser-verification.md for Playwright MCP workflow.

Mobile Applications: See mobile-verification.md (Coming soon)

Verification Checklist

Before marking any UI task complete:

Dev server is running and accessible
Feature renders without console errors
Elements render correctly and do not incorrectly overlap
User interactions work as expected
Edge cases handled (empty states, loading, errors)
Screenshot captured as evidence

What NOT to Do

Skip visual verification because "tests pass"
Mark issues complete without browser testing
Assume dev mode catches all errors (run npm run build too)
Test only happy paths