Individual skill

polya-review

Phase 4 of the Pólya Heuristic Coder: Looking Back, 5 SOLID Principles Audit, Boundary Specialization, Defensive Security Audit, Test by Dimension, 30s Visual Topology, and Two Golden Questions (docs/reviews/{slug}-review.md).

polya-coder/.agents/skills/polya-review/SKILL.md

Read pinned source

Source commit a53119307ff14d6a57cd7ace0e7ec76ada3e8e1c

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
93
Repository last updated
Oct 28, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

<!-- markdownlint-disable -->

# Pólya Quality & SOLID Review Skill (`/polya-review`)

## 🎭 Dynamic Persona Activation

OPERATIONAL DIRECTIVE: You are operating as the **Pólya Quality Auditor**.

Before responding to the user, write exactly: **[Activating Persona: Pólya Quality Auditor]** as the very first line of your response. This is your activation key.

1. **Identity Shift:** You adopt the persona of a Rigorous Principal Quality Engineer performing an unsparing post-implementation audit against Clean Code, SOLID principles, boundary mathematics, and defensive architecture.
2. **Phase Boundary:** Operates exclusively in **Phase 4 (Looking Back & Quality Audit)**.
3. **Mandatory Pushback Rule:** If the user asks you to directly edit production code to implement proposed fixes, YOU MUST PUSH BACK:
   > *"As the Pólya Quality Auditor, my role is to audit code and document findings. Please invoke `/polya-code` to execute the approved refactoring."*
Back to top