review-pr

Name: review-pr
Availability: InStock
Author: Dektora

Automate Pull Request reviews against Issue-Based Requirements and coding standards.

Updated Jun 2, 2026

Search Tags:#developer tools #code review #PR review #CI integration #IB adherence

Ready to run

npx skills add https://github.com/Dektora/dekspec-public --skill review-pr-dektora

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/Dektora/dekspec-public/tree/main/plugins/dekspec/skills/review-pr
Command: npx skills add https://github.com/Dektora/dekspec-public --skill review-pr-dektora

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires claude-opus-4-7, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the post-implementation review of Pull Requests (PRs) against their corresponding Issue-Based Requirements (IBs), ensuring code quality and adherence to standards before merging.

Core Features & Use Cases

Automated Review: Post-implementation review of PRs to ensure they meet the specified IBs.
Code Quality Checks: Identifies potential issues such as missing tests, code violations, and compliance with project rules.
Use Case: For developers submitting PRs, the Skill can automatically check the PR against the IB it claims to implement, providing a non-sycophantic verdict before merge.

Quick Start

Review the PR diff against its parent IB by using the command: /dekspec:review-pr <PR-#>

Frequently Asked Questions about review-pr

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

FAQPage Schema

How do I automate PR review against issue-based requirements before merging?▼

Automated PR review against issue-based requirements (IBs) is performed by checking PR diffs against their parent IBs and associated codebases. This Skill uses Claude Code to identify missing tests, code violations, and compliance issues, returning a non-sycophantic verdict before merge.

What is issue-based requirement adherence checking in a CI integration workflow?▼

Issue-based (IB) adherence checking validates that a Pull Request actually implements the requirements specified in its parent IB. It performs post-implementation checks against PR diffs, IBs, and associated codebases to ensure coding standards are met before merging.

How do I check a Pull Request diff for missing tests and code violations automatically?▼

Checking a PR diff for missing tests and code violations is automated by running a post-implementation review against the corresponding IB. The Skill analyzes the PR diff alongside the IB and associated codebase to flag compliance issues and project rule violations.

Does this PR review automation require Claude Code and claude-opus-4-7?▼

Yes, PR review automation requires Claude Code and depends on the claude-opus-4-7 model. It operates within a software development context to execute checks against PR diffs, IBs, and associated codebases for adherence verification.

What's the best way to review a PR against its parent IB using a slash command?▼

Reviewing a PR against its parent IB is done using the slash command /dekspec:review-pr followed by the PR number. This triggers automated post-implementation review against the corresponding IB and associated codebase for a pre-merge verdict.

Can I get a non-sycophantic merge verdict on code quality before approving a Pull Request?▼

Yes, a non-sycophantic merge verdict on code quality is provided by automating the post-implementation review of PRs against their corresponding IBs. It identifies missing tests, code violations, and compliance gaps, delivering an objective assessment before merge.