App Verification Sub-Agent

VerifiedCaution

Launch a sub-agent that performs end-to-end verification of the application. It checks builds, linting, type errors, runs unit tests, performs manual UI testing via Playwright, and verifies integration points. Ideal for QA verification before release or after changes to ensure app stability and correctness.

Sby Skills Guide Bot
TestingIntermediate
1806/2/2026
Claude CodeCursorWindsurf
#verification#qa#testing#sub-agent#e2e

Recommended for

Our review

Launches a sub-agent to perform end-to-end verification of the application, including build, lint, tests, and manual inspection.

Strengths

  • Provides a systematic and automated check across multiple aspects (build, lint, tests, integration).
  • Integrates a dedicated sub-agent for deep analysis and UI testing via Playwright if available.
  • Generates a structured report with pass/fail results, warnings, and recommendations.

Limitations

  • Requires pre-configured build and test environments.
  • Manual verification with Playwright depends on the availability of the corresponding MCP tool.
  • May not catch advanced performance or security issues.
When to use it

Use this skill before major deployments or releases to ensure application quality.

When not to use it

Avoid for quick checks or when the testing infrastructure is not in place.

Security analysis

Caution
Quality score85/100

The skill instructs a sub-agent to execute common development commands (build, lint, test) that may run arbitrary code from project configuration. While typical for QA automation, this introduces a risk if used in untrusted environments. No overt destructive or exfiltration commands are present.

Findings
  • Running 'npm run build' and similar commands can execute arbitrary scripts defined in package.json, which could be malicious in untrusted repositories.

Examples

Full application verification
Verify the entire application end-to-end, including build, lint, tests, and integration.
Verify login feature
Run a verification sub-agent focused on the login feature: build, lint, unit tests for login, and manual UI testing via Playwright.
Integration check only
Launch a sub-agent to verify API endpoints and database connections for the user service.

Verify App Sub-Agent

Launch a sub-agent to perform end-to-end verification of the application.

Target: $ARGUMENTS (specific feature or general verification)

Instructions for Sub-Agent

You are a QA verification specialist. Your goal is to thoroughly test the application and report any issues.

Verification Steps:

  1. Build Check

    • Run build commands (npm run build, etc.)
    • Verify no compilation errors
    • Check for warnings
  2. Lint & Type Check

    • Run linter (eslint, etc.)
    • Run type checker (tsc, mypy, etc.)
    • Report any issues
  3. Unit Tests

    • Run test suite
    • Report failures and coverage
  4. Manual Verification (if Playwright MCP available)

    • Open the app in browser
    • Test key user flows
    • Take screenshots of important states
    • Verify UI renders correctly
  5. Integration Check

    • Verify API endpoints respond
    • Check database connections
    • Test external service integrations

Output:

Provide a verification report with:

  • ✅ Passed checks
  • ❌ Failed checks with details
  • ⚠️ Warnings or concerns
  • 📝 Recommendations

Use appropriate sub-agents (Explore for code analysis, Playwright for UI testing).

Related skills