pr-verify

Verify PR fixes address prior review feedback without introducing new issues.

12|1|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/apokamo/kaji --skill pr-verify-apokamo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-verify
Source: https://github.com/apokamo/kaji/tree/main/.claude/skills/pr-verify
Command: npx skills add https://github.com/apokamo/kaji --skill pr-verify-apokamo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR レビュー修正後の確認を行う。新規指摘はしない前提で、修正済みの指摘項目が正しく対応され、全体の品質が回復したかを検証します。重要: このスキルは修正を行ったセッションとは別のセッションで実行することを推奨します。

Core Features & Use Cases

  • 修正済み指摘の適切な修正確認と回帰防止
  • 直前のレビューと PR の文脈を比較して変更点を検証
  • フォージ環境のワークフローにおける PR クローズ準備のガードレール

Quick Start

Submit fixes to a PR and run the kaji pr-verify workflow to validate the fixes.

Frequently Asked Questions about pr-verify

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

FAQPage Schema
How do I verify PR fixes without introducing new issues in GitHub?

To verify PR fixes without regressions, run a pr-verify workflow in a separate session to validate that corrections address prior code review feedback and confirm overall quality recovery. It compares the latest pull request changes against previous review context to ensure no new issues are introduced.

What is the best way to check if pull request corrections match prior code review feedback?

The best way to check if pull request corrections match prior feedback is using an automated verification workflow that propagates context from previous reviews. It validates that fixed items are correctly addressed and guards against regressions before closing the PR.

Can I run PR verification in the same session as the code fix?

No, you should not run PR verification in the same session as the code fix. It is recommended to execute the pr-verify workflow in a separate session to properly validate the corrections without context overlap from the modification step.

Does the PR verification workflow raise new code review issues?

No, the PR verification workflow does not raise new code review issues. It operates under the assumption of not introducing new feedback, strictly verifying that previously identified items are correctly fixed and that overall code quality has recovered.

When do I need to run a PR verification step in a forge environment?

You need to run a PR verification step in a forge environment after submitting fixes via a /pr-fix step. It serves as a guardrail for PR closure preparation by enforcing proper handling of PR metadata and validating the applied corrections.