skills.rest
saitoco
saitocoOFFICIAL
Explore all skills by this author →
GitHub

verify

Validate post-merge acceptance criteria and update GitHub Issue checkboxes.

Updated Apr 6, 2026
Search Tags:#automation#workflow#github#verify#ci#issue-management
One-click install
npx skills add https://github.com/saitoco/wholework --skill verify-saitoco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/saitoco/wholework/tree/main/skills/verify
Command: npx skills add https://github.com/saitoco/wholework --skill verify-saitoco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically validates post-merge acceptance criteria and updates Issue checkboxes to reflect verification results.

Core Features & Use Cases

  • Automates the verification of post-merge acceptance criteria across GitHub Issues and PRs.
  • Updates the Issue's checkbox list and posts a structured verification summary for stakeholders.
  • Handles pre- and post-merge flows, auto-retry, partial results, and escalation to manual verification when needed.

Quick Start

Run /verify <issue-number> after merging a PR to automatically verify acceptance conditions and update the Issue.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I automate post-merge verification for GitHub issues?▼

Post-merge verification is automated by validating acceptance criteria against the merged PR and updating the corresponding GitHub issue checkboxes. Running a verify command against the issue number triggers the script-based verification steps and posts a structured summary.

What is the best way to update issue checkboxes after a pull request merge?▼

Updating issue checkboxes after a pull request merge is handled automatically by validating the defined acceptance criteria. The workflow checks the post-merge state, reflects the verification results in the checkbox list, and posts a summary for stakeholders.

Can I auto-retry failed acceptance criteria checks before escalating to manual verification?▼

Auto-retry for failed acceptance criteria checks is supported before escalating to manual verification. The workflow handles partial results during the post-merge flow, automatically attempting retries and only escalating when automated verification cannot confirm the conditions.

Does post-merge verification work with pre-merge pull request workflows?▼

Post-merge verification works with both pre-merge and post-merge pull request workflows. It ensures consistent quality across projects by validating acceptance criteria throughout the GitHub issue and PR lifecycle, applying script-based verification steps defined in the domain files.

How do I trigger the post-merge verification process for a specific GitHub issue?▼

Triggering the post-merge verification process requires running the verify command followed by the specific issue number. This executes the frontmatter-driven discovery and script-based verification steps to validate the conditions and update the issue tracking.

Related Skills

Explore More Software Engineering Skills→
auerbachbauerbachb
3

check-acceptance-criteria

Verify acceptance-criteria checkboxes in GitHub pull requests against repository code.

Community
Advanced
joe-watkinsjoe-watkins
1

a11y-validator

Re-run accessibility tests and verify acceptance criteria against magentaa11y-mcp.

Community
Intermediate
vrcmsvrcms
1

github-ops

Automate GitHub repository management tasks using the GitHub CLI.

Community
Advanced
auerbachbauerbachb
3

wrap

Verify unresolved reviews, squash-merge pull requests, and clean up local worktrees.

Community
Advanced