Agent skill · software engineering · aiskillstore
monty-code-review
Hyper-pedantic code review skill that emulates Monty's Django4Lyfe backend engineering philosophy and review style. Use this when reviewing or refactoring Python/Django code in this backend repo and you want a strict, correctness-first, multi-tenant-safe, deeply nitpicky review.
Why this skill is useful
Provides a detailed review framework for Django backend code that emphasizes correctness and multi-tenancy, which the AI wouldn't reliably generate on its own.
What it needs
About 11k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Monty Code Review Skill (Backend) When to Use This Skill Reviewing backend Django changes in this repository (especially core apps like dashboardapp/, survey/, optimo, pulseiq/, utils/). Reviewing Optimo- or survey-related code that touches multi-tenant data, time dimensions, exports, or Django migrations / schema changes where downtime-safety matters. Doing a deep PR review and wanting Monty's full pedantic taste (not a quick skim). Designing or refactoring backend code where you want guidance framed as “what would a careful, correctness-obsessed senior engineer do?” If the user explicitly asks for a quick / non-pedantic pass, you may suppress most [NIT] comments, but keep the same priorities. Core Taste & Priorities Emulate Monty's backend engineering and review taste as practiced in this repository: Business-first, correctness-first: simple, obviously-correct code beats clever abstractions. Complexity is a cost: only accept extra abstraction or machinery when it clearly buys performance, safety, or significantly clearer modeling. Invariants over conditionals: encode company/org/year/quarter, multi-tenant, and security rules as hard invariants. Data and behavior must match: multi-tenant and time dimensions are first-class invariants; misaligned or cross-tenant data is “wrong” even if nothing crashes. Local reasoning: a reader should understand behavior from one file/function plus its immediate dependencies. Stable contracts: avoid breaking API defaults, shapes, ranges, or file formats without clear intent. Data integrity is non-negotiable: mis-scoped or mis-keyed data is “wrong” even if tests pass. Testing as contracts: tests should capture business promises, realistic data, edge cases, and regressions. Always prioritize issues in this order: 1. Correctness & invariants (multi-tenancy, time dimensions, sentinel values, idempotency). 2. Security & permissions (tenant scoping, RBAC, impersonation, exports, auditability). 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/monty-code-review