Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

verify

Estrellas3

Forks1

Actualizado25 de junio de 2026 a las 18:16

Prove completion claims with fresh evidence. Use with /verify before saying done.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

damian87x

damian87x/oh-my-copilot

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

SKILL.md

readonly

name	verify
description	Prove completion claims with fresh evidence. Use with /verify before saying done.

Verify

Use /verify before saying done.

When to use

You've completed a task and need to prove it works
Someone claims "it's done" and you need to confirm
Before creating a PR or handing off work

Steps

State the claim — what is being verified (e.g. "auth flow works end-to-end")
Run checks — the smallest set of commands/inspections that prove the claim:
- Tests: npm test, pytest, etc.
- Build: does it compile/build without errors?
- Lint: any new warnings?
- Behaviour: does the feature work as described? For web UI flows, use /qa-browse to drive the live page and capture snapshot/screenshot evidence.
Read outputs — don't assume green means pass; read the actual results
Report honestly — if there are gaps, say so

Rules

Fresh evidence only — don't rely on previous test runs
If a check fails, report it as a gap, don't hide it
Verify what was asked for, not more and not less

Output

PASS or FAIL
Evidence — command output, screenshots, or behaviour description
Known gaps — anything not verified and why
Stop condition — what would need to change for a different verdict

Más de este repositorio

mismo repositorio

skill-bench

damian87x/oh-my-copilot

Use when a user wants to compare an arbitrary skill or path across models, quality, cost, latency, or routing.

2026-07-173

history-analyze

damian87x/oh-my-copilot

Analyze actual local Copilot skill activations without reading conversation content.

2026-07-163

wayfinder

damian87x/oh-my-copilot

Plan work too big for one agent session as a shared map of decision tickets on GitHub Issues or Jira, then resolve them one at a time until the route is clear. Use with /wayfinder when the user says "plan something too big for one session", "chart a map", "wayfind", "work the map", or "decision tickets". Always confirm tracker (GitHub vs Jira) and destination before writing. Adapted from mattpocock/skills wayfinder (MIT).

2026-07-163

handoff

damian87x/oh-my-copilot

Create or resume a task handoff so a fresh agent can continue unfinished work. Persist via omp handoff CLI (never write handoff files yourself). Use when the user says /handoff, wants to pause mid-task, or resume prior work.

2026-07-153

ralph

damian87x/oh-my-copilot

Single-owner execute-fix-verify loop for one clear task. Use with /ralph when one agent should keep going until evidence or blocker.

2026-07-053

ultraqa

damian87x/oh-my-copilot

Adversarial QA pass that tests behavior, failures, and regressions. Use with /ultraqa after implementation when shallow checks are not enough.

2026-07-053

name	verify
description	Prove completion claims with fresh evidence. Use with /verify before saying done.

Verify

Use /verify before saying done.

When to use

You've completed a task and need to prove it works
Someone claims "it's done" and you need to confirm
Before creating a PR or handing off work

Steps

State the claim — what is being verified (e.g. "auth flow works end-to-end")
Run checks — the smallest set of commands/inspections that prove the claim:
- Tests: npm test, pytest, etc.
- Build: does it compile/build without errors?
- Lint: any new warnings?
- Behaviour: does the feature work as described? For web UI flows, use /qa-browse to drive the live page and capture snapshot/screenshot evidence.
Read outputs — don't assume green means pass; read the actual results
Report honestly — if there are gaps, say so

Rules

Fresh evidence only — don't rely on previous test runs
If a check fails, report it as a gap, don't hide it
Verify what was asked for, not more and not less

Output

PASS or FAIL
Evidence — command output, screenshots, or behaviour description
Known gaps — anything not verified and why
Stop condition — what would need to change for a different verdict