pr-police

Review git diffs and pull requests for coding standards and anti-patterns.

7|2|Updated Aug 21, 2025
One-click install
npx skills add https://github.com/smallcloudai/flexus-client-kit --skill pr-police
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-police
Source: https://github.com/smallcloudai/flexus-client-kit/tree/main/.claude/skills/pr-police
Command: npx skills add https://github.com/smallcloudai/flexus-client-kit --skill pr-police

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces code quality and best practices by reviewing code changes in pull requests, preventing common mistakes and ensuring adherence to project standards.

Core Features & Use Cases

  • Code Review: Analyzes git diff for potential issues like "best behavior" anti-patterns, generic naming, and poor exception handling.
  • Prompt & Scenario Adherence: Checks if code changes align with bot specifications and improve prompt effectiveness or scenario handling.
  • Use Case: Before merging a new feature, this Skill automatically flags any code that uses overly broad exception catching or unclear variable names, ensuring the codebase remains maintainable and robust.

Quick Start

Use the pr-police skill to review the current staged changes.

Frequently Asked Questions about pr-police

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

FAQPage Schema
How do I review git diffs for anti-patterns and poor exception handling?

Reviewing git diffs for anti-patterns involves analyzing code changes to identify broad exception handling and generic naming. This Skill automatically checks pull requests to enforce coding standards and flags these specific issues.

What is the best way to enforce coding standards in pull requests?

The best way to enforce coding standards in pull requests is to review staged changes against project specifications. This Skill analyzes diffs to ensure code is simple, well-documented, and free of common anti-patterns before merging.

How do I check if my code changes align with bot specifications and prompt quality?

Checking code changes for bot specification alignment involves reviewing diffs to verify prompt effectiveness and scenario handling. This Skill evaluates pull requests to ensure modifications improve prompt quality and adhere to defined behaviors.

Can I use automated code review to flag unclear variable names before merging?

Yes, automated code review can flag unclear variable names before merging. This Skill analyzes git diffs to detect generic naming and enforces best practices, ensuring the codebase remains maintainable and robust.

Does this code review Skill require specific dependencies to analyze staged changes?

No specific dependencies are required to analyze staged changes. This Skill operates directly on git diffs to identify anti-patterns and enforce best practices without needing external modules or additional environment setup.

When should I use automated pull request reviews instead of manual inspection?

Automated pull request reviews should be used when you need to consistently catch broad exception handling and generic naming across features. This Skill provides systematic diff analysis to maintain code quality before merging.