beeui-verify-and-correct

Verifies implemented BeeUI issues, applies minimal in-scope corrections, and returns consolidated review evidence.

Updated May 30, 2026
One-click install
npx skills add https://github.com/beesyst/beeui --skill beeui-verify-and-correct-beesyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beeui-verify-and-correct
Source: https://github.com/beesyst/beeui/tree/main/.agents/skills/beeui-verify-and-correct
Command: npx skills add https://github.com/beesyst/beeui --skill beeui-verify-and-correct-beesyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After an implementation is finished, teams need an independent check that the work actually satisfies the approved task contract without scope creep, unrelated edits, or unverified claims. This Skill performs that post-implementation verification and applies only corrections tied to demonstrated blockers. ## Core Features & Use Cases - Independent acceptance verification: Evaluates every Acceptance Criterion against the actual worktree, diff, tests, and rendered behavior rather than trusting reports. - Scoped correction runs: Treats final-review blocking findings as the complete correction scope, applying minimal fixes with proportional regression checks. - Consolidated evidence report: Returns a structured 19-section report covering changed files, checks, security, dependencies, and final readiness, including a mandatory comment/docstring gate. - Use Case: After a developer finishes a BeeUI issue, run this workflow to confirm the branch, verify each Acceptance Criterion, fix only demonstrated blockers, and produce evidence for the final read-only review. ## Quick Start Ask the agent to independently verify the implemented BeeUI issue in the target worktree against the approved task contract and return the consolidated readiness report.

Frequently Asked Questions about beeui-verify-and-correct

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

FAQPage Schema
How do I verify an implemented issue before final review?

Run this workflow on the exact target worktree with the approved task contract. It checks the branch and git status, evaluates every Acceptance Criterion against current repository evidence, runs required checks, and returns a consolidated readiness report.

How do I fix blocking findings from a code review?

Start a correction run by supplying the explicit blocking findings from the completed final review. The workflow treats those blockers as the complete scope, applies minimal corrections, and verifies regressions only in the touched behavior.

Can this workflow commit, push, or create a pull request?

No. The executor may inspect files, modify the target worktree, and run local checks, but it must not commit, push, create or update a PR, merge, or change the project version unless the issue is explicitly release-related.

What inputs are required for a correction run?

A correction run requires the project, exact target worktree, expected branch, base branch, related-repository contracts, and the explicit blocking findings from the completed final review. It does not require the full issue, planning context, or prior reports.

What are the limitations of this verification workflow?

It cannot expand the approved scope, add optional polish, or make preventive changes without a demonstrated blocker. When a required check cannot be executed, the corresponding evidence is explicitly marked as not verifiable rather than claimed as passed.