pida-code-review
Provides structured code reviews for PIDA, prioritizing API contracts, transaction safety, and regression risks over stylistic concerns.
Install
mkdir -p .claude/skills/pida-code-review && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17282" && unzip -o skill.zip -d .claude/skills/pida-code-review && rm skill.zipInstalls to .claude/skills/pida-code-review
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when reviewing a PIDA branch, diff, or PR. Focus on bugs, regressions, missing tests, API contract drift, persistence risks, and operational issues before style comments.Key capabilities
- →Review PIDA branches, diffs, or pull requests
- →Identify bugs, regressions, and missing tests
- →Detect API contract drift and persistence risks
- →Prioritize findings by severity with file references
- →Check for operational issues before style comments
How it works
The skill reads module boundaries and validation defaults from `./AGENTS.md`, then maps changed modules and reviews behavior risks. It prioritizes findings related to API contracts, auth, transactions, cache, schedulers, external clients, and missing tests or docs.
Inputs & outputs
When to use pida-code-review
- →Reviewing pull requests for regression risks
- →Checking API contract compatibility
- →Validating transaction and null handling logic
- →Ensuring documentation and test coverage
About this skill
PIDA Code Review
Use this skill when the user asks for a review, PR review, regression scan, or pre-merge check in PIDA.
Workflow
- Read
./AGENTS.mdfor module boundaries and validation defaults. - Map changed modules first, then review behavior risks before style.
- Prioritize findings about API contracts, auth, transactions, cache, schedulers, external clients, and missing tests or docs.
- Output findings first, ordered by severity, with file references and a short explanation of impact.
- If no findings exist, say so explicitly and mention residual test or verification risk.
Focus areas
core-api: endpoint path and verb, auth, request validation,ApiResponseAdvice,ApiExceptionAdvice, Swagger annotationscore-api: also flag DTO files that bundle multiple unrelated top-level public classes when they should be split by concerncore-domain: facade or service boundaries, null handling, transaction assumptions, branching logicdb-coreandredis: query filters, soft delete, repository contracts, cache invalidation, lock semanticsclients: request or response DTO compatibility, configuration properties, retry or error handling- tests and docs: matching RestDocs or tests for public API or persistence behavior changes
Notes
- Prefer concrete regressions and missing coverage over style comments.
- Read
references/review-checklist.mdwhen you need the module-by-module checklist or review output shape.
When not to use it
- →When reviewing code that is not part of PIDA
- →When the primary goal is to provide style comments
Limitations
- →Focuses on PIDA-specific code changes
- →Prioritizes concrete regressions and missing coverage over style comments
How it compares
This workflow systematically reviews PIDA-specific architectural components and risks, unlike a general code review that might focus on broader programming principles.
Compared to similar skills
pida-code-review side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| pida-code-review (this skill) | 0 | 4mo | No flags | Intermediate |
| supabase-known-pitfalls | 1 | 10d | Review | Intermediate |
| generating-database-seed-data | 10 | 10d | Review | Intermediate |
| supabase-postgres-best-practices | 4 | 6mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
supabase-known-pitfalls
jeremylongshore
Execute identify and avoid Supabase anti-patterns and common integration mistakes. Use when reviewing Supabase code for issues, onboarding new developers, or auditing existing Supabase integrations for best practices violations. Trigger with phrases like "supabase mistakes", "supabase anti-patterns", "supabase pitfalls", "supabase what not to do", "supabase code review".
generating-database-seed-data
jeremylongshore
Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.
supabase-postgres-best-practices
davila7
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
supabase-common-errors
jeremylongshore
Execute diagnose and fix Supabase common errors and exceptions. Use when encountering Supabase errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "supabase error", "fix supabase", "supabase not working", "debug supabase".
supabase-policy-guardrails
jeremylongshore
Implement Supabase lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Supabase integrations, implementing pre-commit hooks, or configuring CI policy checks for Supabase best practices. Trigger with phrases like "supabase policy", "supabase lint", "supabase guardrails", "supabase best practices check", "supabase eslint".
analyzing-query-performance
jeremylongshore
Execute use when you need to work with query optimization. This skill provides query performance analysis with comprehensive guidance and automation. Trigger with phrases like "optimize queries", "analyze performance", or "improve query speed".