review

Prompt file imported from imvanzen/strava-kudosik (.cursor/commands/review.md). Copyright stays with the author.

Your goal is to review the implementation against the provided implementation plan and feature context.

Make sure to review not only the code and its acceptance criteria but also consider security aspects, code quality, testing coverage, and documentation.

Required Skills

Before starting, load and follow these skills:

• code-review - for the structured code review process covering correctness, quality, security, testing, best practices, and scalability
• implementation-gap-analysis - to compare the implemented solution against the plan and verify completeness
• technical-context-discovery - to understand project conventions and coding standards to review against

Workflow

1. Understand context: Load the *.research.md and *.plan.md files to understand the task requirements and implementation plan. Ensure to review *.instructions.md files for project-specific guidelines.
2. Review implementation: Focus on code correctness, code quality, security, testing, and documentation.
3. Verify definition of done: Check each item from the tasks' definition of done defined in the plan phases. When the definition of done is met, check the box for the completed item in the plan document.
4. Verify acceptance criteria: Check each item from the acceptance criteria checklist in the plan file. When the acceptance criteria is met, check the box for the completed item.
5. Summarize findings: Provide a summary of findings, including any issues identified and recommendations for improvement.
6. Document results: Add findings to the plan file at the end in a new section named "Code Review Findings".
7. Update changelog: Add information that code review was performed to the changelog section of the plan file.

When it comes to updating the definition of done and acceptance criteria checklist, you can only update those by checking the box for completed items. Do not modify the text of those sections.