code-police

Audit pull request code changes against code-police rules for quality and simplicity.

25|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/srid/agency --skill code-police
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-police
Source: https://github.com/srid/agency/tree/main/.apm/skills/code-police
Command: npx skills add https://github.com/srid/agency --skill code-police

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review changes against the project’s code-police rules to catch quality and simplicity issues before merge, reducing defects and rework.

Core Features & Use Cases

  • Rule-driven reviews: checks changes against a growing set of code-police rules (dry-rule-of-three, invalid-states-unrepresentable, no-dead-code, and more) to prevent common mistakes.
  • Three-pass workflow: performs three passes in sequence to surface and address violations in a PR.
  • Guided remediation: produces actionable feedback so engineers can fix issues in subsequent commits.

Quick Start

Run the three-pass code-police review on your current PR to identify and fix violations before merge.

Frequently Asked Questions about code-police

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

FAQPage Schema
How do I check my pull request for code quality and simplicity issues?

To check a pull request for code quality, run a three-pass review that audits changes against rules for complexity, dead code, and anti-patterns. It reports violations with rationale and requires you to address findings before merge completion.

What are the best practices for catching dead code and anti-patterns before a merge?

Catching dead code and anti-patterns before a merge is achieved by applying rule-driven code reviews. A three-pass workflow surfaces violations like invalid states and unrepresentable data so engineers can fix issues in subsequent commits.

Does static analysis of a current branch enforce the dry-rule-of-three?

Static analysis of a current branch enforces the dry-rule-of-three and other code-police rules. It performs three sequential passes on your changes to identify violations and provides guided remediation feedback.

Can I use automated code review to prevent invalid states in my codebase?

Automated code review can prevent invalid states by checking changes against the invalid-states-unrepresentable rule. This prevents common mistakes by ensuring violations are surfaced and addressed prior to merging.

How does a three-pass code review workflow identify violations in a PR?

A three-pass code review workflow identifies violations by performing three sequential checks on your pull request changes. It evaluates the codebase against a growing set of rules, reporting each violation with actionable rationale for remediation.