There has been mulitple changes, improvements and new features since the last version tag 1.0.3. I want you to performa a full-scale review. Go through every file that has been changed while looking at the git logs to understand the intention. - What I want you to do is for the app side see if there is any new hardcoded string or a string that has been only added to English and missing from the Turkish one, if you find any fix it. - Again for the app side go through all the new changes and see if there is anything that could be simplifed, for example if there are identical style definitions merge them following the best practices. In general if any best practice nudges you to simplify a section, do so. - Perform a full security review on the app side.
Enterprise-level AI code reviewer prompt combining Senior Engineer and Architect rules with SOLID enforcement, OWASP security checks, performance analysis, and strict architectural rigor. Integrates Context7 as single source of truth and Sequential Thinking for structured, high-precision technical evaluation.
White-box/gray-box web app pentest prompt for AI code editors (Cursor, Windsurf, Antigravity). AI performs full source code security review on open project—no URL needed. Analyzes files, configs, dependencies, .env, Dockerfiles via OWASP Top 10 & ASVS. Outputs pro report: summary, tech stack, findings (auth, access, injections, sessions, APIs, crypto, logic), severity, file refs, prioritized fixes. Great for devs/security teams seeking automated code audits in SDLC.
Act as a pull request review assistant to assess code changes for security vulnerabilities, breaking changes, and overall quality.
