Run any Skill in Manus with one click

verification-before-completion

Stars134

Forks12

UpdatedMarch 10, 2026 at 18:20

Use before claiming work is complete, fixed, or passing in Cursor. Requires fresh verification evidence such as tests, builds, lint output, or direct reproduction checks.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

6BNBN

6BNBN/FlowPilot

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	verification-before-completion
description	Use before claiming work is complete, fixed, or passing in Cursor. Requires fresh verification evidence such as tests, builds, lint output, or direct reproduction checks.

Verification Before Completion

Rule

Do not claim success without fresh evidence.

Checklist

Identify what command or action proves the claim.
Run it now, not from memory.
Read the result carefully.
Report the real status.

Examples

Tests pass: only after running the relevant test command.
Bug fixed: only after reproducing the original issue path and seeing the correct behavior.
Build succeeds: only after a successful build.
Review complete: only after actually checking the relevant files or diff.

Avoid

"Should be fixed now"
"Looks good"
"Probably passes"
trusting stale output

More from this repository

same repository

brainstorming

6BNBN/FlowPilot

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

2026-03-10134

code-review

6BNBN/FlowPilot

Use when the user asks to review a pull request or diff with a structured Codex CLI workflow using parallel review passes and filtered actionable findings.

2026-03-10134

dispatching-parallel-agents

6BNBN/FlowPilot

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.

2026-03-10134

executing-plans

6BNBN/FlowPilot

Use when you have a written implementation plan to execute in a separate session with review checkpoints

2026-03-10134

feature-dev

6BNBN/FlowPilot

Use when the user asks to build a new feature and wants a structured Codex CLI workflow with discovery, clarifying questions, architecture comparison, implementation, and review.

2026-03-10134

finishing-a-development-branch

6BNBN/FlowPilot

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

2026-03-10134

name	verification-before-completion
description	Use before claiming work is complete, fixed, or passing in Cursor. Requires fresh verification evidence such as tests, builds, lint output, or direct reproduction checks.

Verification Before Completion

Rule

Do not claim success without fresh evidence.

Checklist

Identify what command or action proves the claim.
Run it now, not from memory.
Read the result carefully.
Report the real status.

Examples

Tests pass: only after running the relevant test command.
Bug fixed: only after reproducing the original issue path and seeing the correct behavior.
Build succeeds: only after a successful build.
Review complete: only after actually checking the relevant files or diff.

Avoid

"Should be fixed now"
"Looks good"
"Probably passes"
trusting stale output