verify-test

Detect code changes and update test plans and tests in parallel.

2|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/potenlab/marketplace-potenlab --skill verify-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-test
Source: https://github.com/potenlab/marketplace-potenlab/tree/main/plugins/potenlab-workflow/skills/verify-test
Command: npx skills add https://github.com/potenlab/marketplace-potenlab --skill verify-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps test plans and test files in sync after code changes by automatically detecting changes, comparing with test-plan.md, and orchestrating QA specialists to update tests.

Core Features & Use Cases

  • Detects changes (git diff, changes.json) and determines affected features.
  • Updates test-plan.md with updated scenarios and new tests.
  • Spawns qa-specialist agents to edit or create tests in /features, /tests, /supabase, in parallel for speed.

Quick Start

Invoke /verify-test after you modify code or test files to align tests with new behavior.

Frequently Asked Questions about verify-test

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

FAQPage Schema
How do I keep test plans in sync after modifying code?

To keep test plans in sync after modifying code, this automation reads git diff and changes.json to detect affected features, then updates test-plan.md with revised scenarios and new tests automatically.

What is the best way to automate test updates across multiple feature directories?

The best way to automate test updates across directories is by spawning parallel qa-specialist agents that edit or create tests simultaneously in /features, /tests, and /supabase, ensuring rapid alignment with new behavior.

How does automated test verification detect which features need new tests?

Automated test verification detects affected features by reading changes.json and running git diff to identify code modifications, comparing those changes against the existing test-plan.md to determine missing test coverage.

Can I run parallel QA agents to update tests in supabase and features folders?

Yes, you can run parallel QA agents to update tests in supabase and features folders. The Skill spawns qa-specialist agents in parallel to edit or create tests across /features, /tests, and /supabase directories simultaneously.

When do I need to trigger automated test verification for my code changes?

You need to trigger automated test verification whenever you modify features or test files and require automated test updates, plan revisions, and parallel QA edits to align tests with the new behavior.