verify

Spawns the hardware-verifier agent for a package's most recent pull request.

Updated Dec 27, 2025
One-click install
npx skills add https://github.com/HendrikGC02/Astroray --skill verify-hendrikgc02
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/HendrikGC02/Astroray/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/HendrikGC02/Astroray --skill verify-hendrikgc02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that a package's pull request actually works on real hardware requires manually locating the PR, resolving its worktree and commit SHA, and extracting acceptance criteria from the package spec. This Skill automates that preparation and hands off a complete, correct context to the hardware-verifier agent. ## Core Features & Use Cases - PR Discovery: Finds the package's most recent open or closed pull request using the GitHub CLI. - Spec Extraction: Reads the package spec at .astroray_plan/packages/<pkg>*.md to pull the acceptance gate list and most recent binding for smoke-checking. - Worktree Resolution: Resolves the PR's branch worktree path and head SHA, verifying the worktree exists via git worktree list. - Reactive Mode: Can be triggered automatically when a PR carries the needs-verifier label, extracting the package name from the PR title. - Use Case: After a package PR is opened in the Astroray renderer repository, run the verify command to dispatch a hardware-verifier agent with the correct worktree, expected SHA, and acceptance gates. ## Quick Start Run /verify pkg241 to spawn the hardware-verifier agent for that package's most recent pull request.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify a package pull request on hardware?▼

Run /verify followed by the package name, such as /verify pkg241. The skill finds the package's most recent PR, resolves its worktree and head SHA, extracts acceptance gates from the package spec, and spawns the hardware-verifier agent with that context.

How does the verify skill find the right pull request?▼

It searches open PRs first with gh pr list --search for the package name, then checks recently closed PRs if needed. It resolves the PR's headRefName and headRefOid via gh pr view to identify the exact commit to verify.

Can verification be triggered automatically on a pull request?▼

Yes, reactive mode triggers verification when a PR carries the needs-verifier label. In that case the package name is extracted from the PR title rather than being supplied as a command argument.

What information is passed to the hardware-verifier agent?▼

The agent receives the worktree absolute path, the expected head SHA, the PR number, the package spec path, and the most recent binding name. The binding is used for a smoke-check step during verification.

What happens if the PR worktree does not exist?▼

The skill expects the worktree at .claude/worktrees/<pkg> as the branch's registered worktree and confirms its presence with git worktree list. If it is missing, the worktree must be created before verification can proceed.