Verify

Run a verification iteration — pick something that needs verifying, verify it CU-free, and complete its gate. Use this skill whenever the user wants to verify a shipped feature or bug fix, asks 'verify feature #N', 'verify bug #N', 'run device verification', 'work the verification backlog', or 'close the awaiting-device-verification issues' — and whenever the verify cron fires. Covers BOTH bug close-gate verification (awaiting-device-verification GH issues → closed) and feature Gate-5 verification (docs/features.md DONE → VERIFIED). Verification-only: files bugs, never fixes them; fix work bel

49 stars 21 forksWriting & Content

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lllyys/vreader --skill verify
Manual install
git clone --depth 1 https://github.com/lllyys/vreader.git /tmp/vreader
mkdir -p ~/.claude/skills
cp -r /tmp/vreader/.claude/skills/verify ~/.claude/skills/verify

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Verify

Run one verification iteration: pick something that needs verifying, verify it
against its own contract — CU-free, through the XCUITest + DebugBridge harness —
and complete the gate (close the GH issue, or flip the tracker row).

**Verification only.** If you discover a bug, FILE it (GH issue + `docs/bugs.md`
row, per the triage workflow) — never fix it. Fixes are the bugfix cron's job
(`/fix-issue`).

## Input

Parse the request for an explicit target:

- `verify #443` / `verify bug 154` → verify that specific bug (Mode A).
- `verify feature 65` → verify that feature (Mode B).
- No target (the cron case) → auto-pick per **Pick order** below.

## Two verification modes

| Mode | Target | Gate | Terminal action |
|---|---|---|---|
| **A — Bug close-gate** | open GH issue labeled `awaiting-device-verification` | AGENTS.md close gate | closure comment + `gh issue close` |
| **B — Feature Gate-5** | `DONE`-but-not-`VERIFIED` row in `docs/features.md` | rule 47 Gate 5 | evidence file + row → `VERIFIED` |

A merged fix or feature is *not done* until verified. Mode A clears the
`awaiting-device-verification` debt — AGENTS.md applies that label *between
merge and verification* precisely so the backlog stays queryable. Mode B turns
a merged feature into an accepted one.

## Pick order (when no explicit target)

1. **Mode A — the `awaiting-device-verification` backlog first.**
   `gh issue list --label awaiting-device-verification --state open`. It is
Read the full skill on GitHub

Details

Skill name
verify
Repository
lllyys/vreader
Path
.claude/skills/verify/SKILL.md
Repo updated
6 August 2026

FAQ

What does the Verify skill do?

Run a verification iteration — pick something that needs verifying, verify it CU-free, and complete its gate. Use this skill whenever the user wants to verify a shipped feature or bug fix, asks 'verify feature #N', 'verify bug #N', 'run device verification', 'work the verification backlog', or 'close the awaiting-device-verification issues' — and whenever the verify cron fires. Covers BOTH bug close-gate verification (awaiting-device-verification GH issues → closed) and feature Gate-5 verification (docs/features.md DONE → VERIFIED). Verification-only: files bugs, never fixes them; fix work bel

How do I install the Verify skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add lllyys/vreader --skill verify. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Verify popular?

It lives in lllyys/vreader, which has 49 GitHub stars and 21 forks.

Related skills

AI Coding Agents

49

lllyys/vreader

Comprehensive guide for using Codex CLI (OpenAI) and Claude Code CLI (Anthropic) - AI-powered coding agents. Use when orchestrating CLI commands, automating tasks, configuring agents, or troubleshooting issues.

AI, LLMs & Agents21

Dispatch

49

lllyys/vreader

Parallel lane dispatch — the ONLY sanctioned multi-item fan-out (feature #130, rule 55). Use when the user asks to fix several bugs at once ('fix #a #b #c'), implement independent feature WIs in parallel, or run a dispatch batch. Orchestrates worktree-isolated implementer lanes on leased simulators, validates HANDOFFs, and runs the serial integration tail (rebase → re-test → tracker/docs → version-at-slot → PR → merge-from-worktree → tag). A single item degrades to the inline /fix-issue or /feature-workflow flow.

Git & Code Review21

Feature Workflow

49

lllyys/vreader

Run the binding 6-gate feature workflow end-to-end per rule 47 (Plan → Independent Plan Audit → TDD Implementation → Implementation Audit Loop → Device/Integration Verification → Merge). Use this skill whenever the user wants to implement a new feature in vreader, asks 'implement feature #N', 'work on feature 47', 'start the feature workflow', 'plan + build feature X', or describes building a new capability that doesn't yet exist. NOT for fixing broken implementations (that's fix-issue). The skill drives the row from `TODO` → `VERIFIED` through six gates that must never be skipped — author/aud

Productivity & Notes21

Game Localization Manager

57

AlterLab-IEU/AlterLab_GameForge

Plans and runs game localization: i18n architecture, string extraction per engine, a machine translation + LLM + human review pipeline, pseudo-localization in CI, fonts, RTL and CJK, LQA, and Steam AI disclosure for translated text. Use for "localization", "translation", "i18n", "RTL", "CJK", "pseudo-localization". Not for writing dialogue (use game-narrative-director).

Writing & ContentIn 1 list

Using Isometric Skills

49

0xheycat/isometric-game-skills

Use when starting ANY isometric game task to route the request to the correct specialized skill before writing code or generating art.

Writing & ContentIn 1 list

Game Reverse Document

57

AlterLab-IEU/AlterLab_GameForge

Generates docs from an existing game codebase as a forked report writer: reverse-engineered GDD, architecture overview with ADR drafts, concept document, or a one-page brief for new teammates and coding agents (Godot, Unity, Unreal, web). Use for "document this codebase", "generate docs from code", "onboard me to this codebase". Not for new designs (use game-gdd-author).

Writing & ContentIn 1 list

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.