qa

Report PASS/FAIL QA checks for Scaffold-ETH 2 dApps post-build.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/involvex/aetheris --skill qa-involvex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/involvex/aetheris/tree/main/.agents/skills/ethskills/qa
Command: npx skills add https://github.com/involvex/aetheris --skill qa-involvex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-ship QA audit for Ethereum dApps built with Scaffold-ETH 2, providing a fresh-review context to catch bugs before release and validate against baseline LLM checks.

Core Features & Use Cases

This skill is designed for post-build review, handed to a new reviewer agent after the dApp is built. The reviewer reads the source code (app/, components/, contracts/), runs the app to verify flows, and reports PASS/FAIL for a suite of checks including wallet flow, four-state button flow, branding, contract address display, address inputs, USD value display, OG image URIs, RPC/polling configuration, dark-mode handling, mobile wallet deep linking, and button loading behavior. Use cases include validating an initial release candidate, reproducing critical UX and security checks, and ensuring the app adheres to a strict, verified QA standard.

Quick Start

After the build completes, hand this to a fresh reviewer agent to perform a comprehensive pre-ship audit following the listed rules.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I run pre-ship QA checks for a Scaffold-ETH dApp?

Pre-ship QA for a Scaffold-ETH dApp involves handing the completed build to a fresh reviewer agent that inspects source code, runs the app, and reports PASS/FAIL on checks like wallet flows, contract verification, and button states.

What critical UI and security checks should an Ethereum dApp pass before release?

Critical pre-release checks for an Ethereum dApp include validating wallet connection flows, four-state button behavior, contract address display, USD value rendering, RPC/polling configuration, and mobile wallet deep linking.

Does the Scaffold-ETH QA review validate mobile deep linking and wallet flows?

Yes, the Scaffold-ETH QA review validates mobile wallet deep linking alongside wallet connection flows, ensuring the dApp correctly handles user authentication and transaction signing across mobile environments.

How do I audit an Ethereum dApp for correct contract verification and RPC polling?

To audit an Ethereum dApp for contract verification and RPC polling, a reviewer agent inspects source code and app behavior, enforcing PASS/FAIL results on RPC/polling configuration and contract address display.

What is the best way to enforce consistent branding and dark-mode handling in a Scaffold-ETH 2 application?

Enforcing branding and dark-mode handling in a Scaffold-ETH 2 application is achieved by running a pre-ship QA audit that checks source components and reports PASS/FAIL against strict baseline UI/UX standards.

Why does my dApp need a fresh reviewer context after the build is complete?

A dApp needs a fresh reviewer context after the build to catch bugs before release without developer bias, validating the initial release candidate against baseline LLM checks for critical UX and security issues.