
I've reviewed hundreds of codebases and PRs across Python, JavaScript, C#, TypeScript, Go, Rust, and more. I've distilled that debugging and code review judgment into this skill to help you find bugs, spot security vulnerabilities, and improve code quality before merging.

I have spent more than 25 years in programming and web development, with a strong focus on performance, security, and writing lean code that does not waste resources. Good code should be clear, fast, safe, and practical to maintain. That same mindset is what I bring to this skill.

Your AI built the app. Find out if it is ready to ship. Audits apps built with Cursor, Claude Code, Lovable, Bolt or v0 and ranks what will break after launch, worst first: auth holes, IDOR, Supabase RLS, exposed secrets (always masked), SQL/NoSQL/command injection, SSRF, XSS, payment webhooks and deploy blockers, plus SEO and AI-search readiness. Get a ship decision, scores, evidence-backed findings (file:line) and copy-paste fix prompts. Audit-only; your code is never executed.

Review a diff or pull request for real bugs before merge: four reviewer lenses (one model applying each in turn) check each other and tag findings CONFIRMED, CORROBORATED or DISPUTED.

Upload any UI screenshot — landing page, app screen, dashboard, mockup — and get a principal-level critique before you ship. 10-dimension diagnosis (hierarchy, typography, spacing, alignment, color, contrast, consistency, imagery, interaction, accessibility) with Ship / Fix / Broken verdicts; Top 3 fixes with exact values; Refinement, Conviction, Resilience; Principal Craft Score 1–10, justified. Built by a principal-level product designer. For designers, founders, PMs.

A senior-engineer-style code review assistant: severity-ranked findings, security smell detection, and constructive feedback across 8 language families.

Turn open-ended survey responses into a reviewable codebook, coded CSV, theme summary, quote table, and insight deck outline. 将开放式问卷回答整理成可人工复核的 codebook、编码表、主题摘要、引用表和洞察汇报大纲。No fabrication, no PII leakage, no statistical overclaiming.

Guides, a 56-item checklist, a ready PR template, and a fill-in team policy for code review culture. Includes 10 good/bad comment pairs and 30 situational review comments, unified by a blocker/suggestion/nit/question/praise severity system.
