test-staging-branch_skill

This skill automates end-to-end testing of feature branches on Vercel previews using Chrome automation and Gmail OTP, with sanitized reporting.

TypeScript

186

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill different-ai/agent-bank --skill test-staging-branch

SKILL.md13.8 KB

Overview

This skill tests feature branches on Vercel preview deployments using Chrome automation and Gmail OTP flows. It automates waiting for deployments, logging in via a Gmail OTP, running UI/API checks, and posting sanitized results to GitHub. The workflow is optimized to minimize costly Chrome snapshots and avoid leaking sensitive data.

How this skill works

The skill polls Vercel for the branch preview and waits until the deployment reports Ready. It uses Chrome MCP to drive the app: navigate, take minimal snapshots, use evaluate_script for data extraction (OTP, balances), and complete the Privy/Gmail OTP login flow. After verifying features, it captures local evidence and posts a sanitized test summary as a GitHub PR comment.

When to use it

Validate UI and API changes on a branch preview before merging
Automate login flows that require Gmail OTP verification
Run end-to-end checks after CI completes but before production release
Collect local screenshots and structured verification evidence for PRs

Best practices

Minimize snapshots: use one snapshot per page state and prefer evaluate_script for data
Reuse open tabs with chrome_select_page instead of opening new pages
Wait for vercel inspect --wait to report Ready before testing
Never include emails, OTPs, balances, API keys, or tokens in reports
Sanitize error messages and store screenshots locally only

Example use cases

Check that the Spendable/Earning/Idle balance UI displays and sums correctly on a preview
Automate Privy sign-in with Gmail OTP to access protected preview pages
Verify a new balance endpoint returns expected JSON schema on the preview deployment
Post a sanitized test result to the PR with checklist items and local screenshot references

FAQ

You need Chrome DevTools MCP configured, Vercel CLI authenticated for the project scope, access to the Gmail account for OTP retrieval, and gh (GitHub CLI) authenticated.

How do I avoid wasting tokens on snapshots?

Use chrome_wait_for to detect page state and chrome_evaluate_script to extract text or OTPs. Take snapshots only when you need UIDs or visual evidence.