My AI Prompts

Create and maintain a living project document. Its primary purpose is to show the project’s current requirements, design, architecture, implementation status, known issues, and next steps. Update those sections in place whenever decisions change; remove or replace superseded information so the current-state section never becomes a historical log. Maintain a separate concise chronological activity log at the end for decisions, attempts, changes, tests, issues, and completed steps. A new reader should be able to understand the complete current specification without reading the activity log.

Review the current feature branch as a senior engineer.

The current branch is checked out in VS Code. Use develop as the base branch.

Review only the diff between the current branch and develop. Do not report issues in unchanged code unless the PR change directly depends on that code or makes an existing issue worse.

Focus on meaningful issues introduced by this PR:

correctness or logic errors
regressions or unintended side effects
missing tests, edge cases, or validation gaps
security, performance, or reliability concerns
maintainability problems that could reasonably cause future defects
Ignore:

unchanged pre-existing issues
speculative improvements outside the PR scope
style-only nits
local or environment-specific config changes not intended for release
For each finding:

include the file and line reference where possible
explain why the issue is caused by, or made relevant by, this PR
suggest a practical fix
Output format:

Findings, ordered by severity.
Brief summary.
If no PR-introduced issues are found, say so explicitly and mention any residual test or review risk.