agent-peer-review-checker

Verifies code review compliance by tracking comments and analyzing diffs for blockers and force-pushes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/seqis/OpenClaw-Skills-Converted-From-Claude-Code --skill agent-peer-review-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-peer-review-checker
Source: https://github.com/seqis/OpenClaw-Skills-Converted-From-Claude-Code/tree/main/skills_tree/agent-peer-review-checker
Command: npx skills add https://github.com/seqis/OpenClaw-Skills-Converted-From-Claude-Code --skill agent-peer-review-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all code review feedback is properly addressed and verified before code is merged, preventing issues from slipping through the cracks.

Core Features & Use Cases

  • Comment Tracking: Monitors all review comments and their resolution status.
  • Change Verification: Uses diff analysis to confirm requested changes are implemented.
  • Compliance Reporting: Generates reports detailing review status and adherence to rules.
  • Use Case: Before merging a pull request, use this skill to automatically verify that all blocking comments from the code review have been resolved and that no force-pushes have occurred since the review began.

Quick Start

Use the agent-peer-review-checker skill to verify compliance for the current pull request.

Frequently Asked Questions about agent-peer-review-checker

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

FAQPage Schema
How do I verify code review compliance before merging a pull request?

Code review compliance is verified by systematically tracking comments, confirming required approvals are obtained, and using diff analysis to check that all blocking issues are resolved before merge.

What is the best way to check if code review comments are actually resolved in the diff?

Checking if code review comments are resolved requires change verification through diff analysis, systematically comparing the proposed changes against the requested feedback to ensure all modifications are implemented correctly.

How do I detect force-pushes that bypass code review rules?

Detecting force-pushes that bypass code review involves monitoring the git history for unauthorized overwrites, ensuring that no changes were forcefully pushed to circumvent the blocking issues identified during the review.

Can I generate a compliance report detailing pull request review status?

Generating a compliance report is supported by categorizing tracked review comments and analyzing the diff, which produces a detailed report on the pull request's adherence to required rules and approval statuses.

Does this code review checker require any specific git dependencies to work?

This code review checker requires no external dependencies, operating directly to track comments and verify diff changes, ensuring required approvals and blocking issues are managed without additional environment setup.