verify

Verify Next.js app runtime across boot, auth routes, cron dispatch, and browser flows.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/farzanmrz/beat-radar-agent --skill verify-farzanmrz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/farzanmrz/beat-radar-agent/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/farzanmrz/beat-radar-agent --skill verify-farzanmrz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you verify that a repository's app actually works at its real runtime surfaces, rather than only compiling successfully. It is designed to catch issues in boot behavior, authenticated routes, cron dispatching, and browser-visible UI flows.

Core Features & Use Cases

  • End-to-end runtime verification: Boots the app, checks for clean startup, and sweeps logs for failures.
  • API route validation: Tests the anonymous /api/chat auth gate and the /api/cron/tick authorization and fail-closed behavior.
  • Browser workflow checks: Confirms login, onboarding chat behavior, dashboard tabs, pause/resume state changes, scan execution, and trace visibility.
  • Use case: After changing routing, auth, or scheduling logic, use this Skill to prove the change works in the browser and on live endpoints, not just during build time.

Quick Start

Use the verify skill to run this repository's app checks end-to-end and report whether boot, API authorization, cron dispatch, and browser UI flows are working.

Frequently Asked Questions about verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Next.js app changes at runtime beyond build-time compilation?

Runtime verification boots the Next.js app, checks startup logs, and tests authenticated API routes, cron dispatch, and browser UI flows to prove changes work live. This catches boot behavior and routing issues that compilation misses.

Can I test cron authorization and fail-closed behavior for my API routes?

Yes, API route validation tests the /api/cron/tick authorization and fail-closed behavior, along with the anonymous /api/chat auth gate. This ensures scheduled jobs and authenticated endpoints reject unauthorized requests correctly.

What's the best way to check login and dashboard interactions in a Next.js app?

Browser workflow checks confirm login, onboarding chat behavior, dashboard tabs, pause/resume state changes, scan execution, and trace visibility. This end-to-end validation sweeps console errors to prove UI flows work.

Does end-to-end verification require clean startup checks for streaming chat applications?

End-to-end verification requires clean startup checks and sweeps logs for failures when testing streaming chat applications. It validates boot behavior and live endpoints to ensure changes work at real runtime surfaces.

Why does my Next.js app compile successfully but fail during browser interaction tracing?

Build-time compilation does not test runtime surfaces like browser interaction tracing, authenticated routes, or cron dispatch. Runtime verification boots the app and sweeps for console errors to catch failures that compilation cannot detect.