review▌

Comprehensive App Store review preparation guide covering rejections, privacy manifests, IAP rules, and compliance checklists. \n \n Covers top rejection reasons (incomplete apps, inaccurate metadata, private API usage) with prevention strategies and real examples of approved vs. rejected content \n Detailed privacy manifest requirements with reason codes, ATT implementation patterns, and cross-reference checks between nutrition labels and actual data collection \n In-App Purchase and StoreKit r

Review requirements or plan documents through multi-persona analysis. Dispatches specialized reviewer agents in parallel, auto-fixes quality issues, and presents strategic questions for user decision.

Technical rigor in code review: receiving feedback critically, requesting systematic reviews, and verifying before any completion claims. \n \n Three core practices: receiving feedback with technical evaluation over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before status claims \n Includes decision tree and protocols for handling feedback from human partners versus external reviewers, with explicit rules against performative

Systematic checklist for reviewing code across functionality, security, performance, and maintainability. \n \n Covers six review areas: context understanding, functionality verification, code quality assessment, security checks, performance analysis, and test coverage validation \n Includes concrete examples of common issues (SQL injection, missing validation, unclear naming) paired with corrected versions \n Provides pre-review, per-section, and git-specific checklists to ensure nothing is mis

Identify and review overdue Google Tasks requiring immediate attention. \n \n Requires the gws-tasks skill to query Google Tasks API \n Three-step workflow: list all task lists, filter incomplete tasks by list ID, and review due dates for prioritization \n Returns task data in table format for easy scanning of overdue items \n

Peer review is a systematic process for evaluating scientific manuscripts. Assess methodology, statistics, design, reproducibility, ethics, and reporting standards. Apply this skill for manuscript and grant review across disciplines with constructive, rigorous evaluation.

Automated code review and refactoring against project-specific coding guidelines and instructions. \n \n Reads coding standards from .github/instructions/*.md and .github/copilot-instructions.md to establish project conventions \n Performs comprehensive code review and refactoring to align with defined guidelines while preserving file structure \n Validates that existing tests continue to pass after refactoring changes \n Maintains code integrity by keeping files intact rather than splitting or

Comprehensive C#/.NET design pattern analysis with actionable improvement recommendations. \n \n Evaluates six core patterns: Command, Factory, Dependency Injection, Repository, Provider, and Resource patterns against GoF and SOLID principles \n Analyzes architecture compliance including namespace conventions, project separation, async/await patterns, and structured logging implementation \n Reviews code quality across security, testability, maintainability, and performance dimensions with speci

Evaluate code review feedback with technical rigor before implementing, avoiding performative agreement and blind implementation. \n \n Verify feedback against actual codebase behavior, test coverage, and architectural context before proceeding \n Ask for clarification on unclear items before implementing anything; partial understanding leads to wrong fixes \n Push back on suggestions that break functionality, lack context, violate YAGNI, or conflict with established decisions using technical re

You are a business advisor channeling the philosophy of The Minimalist Entrepreneur by Sahil Lavingia. Review the user's decision or situation through the minimalist entrepreneur framework.