skills.rest
sagittaras
sagittarasOFFICIAL
Explore all skills by this author →
WebsiteGitHub

verify-issue

Verifies pull requests against issue acceptance criteria with mutation testing.

Updated Aug 7, 2026
Search Tags:#code review#pull request#github#acceptance criteria#mutation testing#gitea#issue verification
One-click install
npx skills add https://github.com/sagittaras/agentic-workflow --skill verify-issue-sagittaras
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-issue
Source: https://github.com/sagittaras/agentic-workflow/tree/main/skills/verify-issue
Command: npx skills add https://github.com/sagittaras/agentic-workflow --skill verify-issue-sagittaras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging a pull request on trust alone lets unmet acceptance criteria slip through. This Skill independently proves whether a PR actually satisfies every acceptance criterion of its linked issue, instead of relying on checked boxes, PR descriptions, or commit messages. ## Core Features & Use Cases - Criterion-by-criterion verification: Runs the project's configured verification commands, reads cited code precedents, and demands concrete evidence (command output, file:line references) for each acceptance criterion. - Mutation testing of regression tests: Reverts the production change via git and confirms the new regression test actually fails, proving the test guards what it claims. - Tracker integration: Checks off only verified criteria in the issue body and posts a verdict report (Pass / Needs work / Blocked) with a machine-readable "Blokuje merge" line as a PR comment on GitHub or Gitea. - Use Case: In a milestone run, before merging PR #42 that closes issue #38, invoke the Skill to verify each acceptance criterion in an isolated worktree and receive a merge-blocking verdict without touching the working tree. ## Quick Start Verify that PR 42 fulfills the acceptance criteria of its linked issue and post the verdict as a PR comment.

Frequently Asked Questions about verify-issue

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

FAQPage Schema
How do I verify a pull request against issue acceptance criteria?▼

Invoke the Skill with an issue number, PR number, or branch name. It locates the issue-PR pair, checks out the PR branch in an isolated worktree, runs the configured verification commands, and posts a Pass, Needs work, or Blocked verdict as a PR comment.

What is mutation testing of regression tests?▼

Mutation testing reverts the production change with git apply -R and reruns the test suite. If the new regression test still passes with the fix reverted, it guards nothing and the criterion is marked unmet; otherwise the tree is restored and the test must pass again.

Does it work with both GitHub and Gitea?▼

Yes. On GitHub it calls gh-based scripts from the plugin's scripts directory with an explicit -R owner/repo flag. On Gitea it loads a restricted set of mcp__gitea__ tools via ToolSearch, deliberately excluding any PR write or merge capability.

Can the Skill fix issues it finds during verification?▼

No. It is strictly read-only: it never edits code, adds tests, or modifies the PR. Findings are routed as recommendations to implement-issue or triage-issue, keeping the verifier independent from the author of the change.

Why does verification fail with a Blocked verdict?▼

Blocked means verification could not run as a whole: missing workflow configuration, no area label or verification command for the issue, an unresolvable issue-PR pair, an unavailable PR branch (such as fork PRs), or an environment that cannot execute the verification command.

What are the limitations for pull requests from forks?▼

PRs from forks cannot be verified because git fetch only reaches branches of the same repository. The Skill reports this as a structural limitation in the verdict rather than a failure of the PR itself.

Related Skills

Explore More Software Engineering Skills→
pkuppenspkuppens

integration-pr

Open pull requests linked to issues with Summary and Changes sections.

Community
Intermediate
pekralpekral

merge-github-pr

Merge eligible GitHub pull requests after validating mergeability, CI checks, and approvals.

Community
Intermediate
silcamsilcam

quality-review

Review pull request diffs for code quality and test coverage.

Official
Advanced
imclabimclab
1

qa-plan

Generate structured QA test plans from sprint stories and GDD acceptance criteria.

Official
Advanced