flow

Verifies code changes end-to-end with tests, browser checks, and a verdict report.

3|1|Updated Aug 23, 2025
One-click install
npx skills add https://github.com/samuelpatro/.claude --skill flow-samuelpatro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flow
Source: https://github.com/samuelpatro/.claude/tree/main/skills/flow
Command: npx skills add https://github.com/samuelpatro/.claude --skill flow-samuelpatro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually confirming that a code change actually works is slow and error-prone: you must inspect the diff, run the right tests, start the app, click through affected pages, and piece together a conclusion. This Skill automates that entire QA loop and reports a clear verdict with evidence. ## Core Features & Use Cases - Change Set Resolution: Works against uncommitted changes, a PR number/URL, a branch/ref, or a worktree path, extracting acceptance criteria from PR bodies when available. - Test Execution: Runs the project's own test runner scoped to the change, surfacing failures prominently without halting the flow. - Browser Verification: Drives a browser over every affected surface, capturing both DOM/network assertions and viewed screenshots as evidence. - Structured Verdict Report: Produces a status table with ✅/❌/⚠️/⏭️ icons, change summary, detailed failures, and nitpicks with file:line references. - Use Case: Before merging a PR that touches login templates and a checkout endpoint, run the flow to confirm tests pass, pages render without console errors, and receive a screenshot-backed verdict. ## Quick Start Ask the agent to verify the current working changes or a specific PR end-to-end and report whether it works.

Frequently Asked Questions about flow

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

FAQPage Schema
How do I verify a pull request works before merging?▼

Pass the PR number or URL as the target. The flow fetches the PR diff and acceptance criteria via gh, runs the relevant tests, serves the app, drives a browser over affected pages, and reports a verdict with screenshots.

How to smoke-test uncommitted changes in a worktree?▼

Run the flow with no argument to verify current working changes from git status and git diff HEAD. It classifies the changed files, runs scoped tests, and browser-tests any UI surfaces the diff touches.

Does the verification flow modify my repository or branches?▼

No, the flow is strictly read-only on the repository. It performs no checkout, stash, reset, pull, commits, or new worktrees; it only observes the current worktree and reports findings.

What happens if tests fail during end-to-end verification?▼

Failing tests do not stop the flow. The run continues through app launch and browser checks, and the failures are surfaced prominently in the verdict table with verbatim output in the detail section.

Can it verify backend or library changes without a UI?▼

Yes. Non-UI changes such as libraries, CLIs, and pure backend code are verified through tests and direct command runs instead of browser checks, and the report notes that browser verification was not applicable.

Why is a screenshot alone not enough for UI verification?▼

The flow requires both DOM/network assertions and a viewed screenshot per surface. DOM checks prove behavior but miss rendering issues, while an unviewed screenshot counts as not taken; DOM-only verification is marked as a caveat.