**First, ensure we're up to date:** ```bash git fetch git status ``` Confirm and display the current feature branch name. --- **Then run the code review:**
Installs into .claude/skills of the current project.
Are you the author of 2541 Implementation Review 9f330b77?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/tools-only-2541-implementation-review-9f330b77)
---
allowed-tools: Bash(git fetch:*), Bash(git status:*), Bash(git diff:*), Read, Glob, Grep
workflow-stage: code-review
suggested-next:
- discuss -> commit_push -> implementation_approve
- discuss -> implementation_new_tasks -> commit_push -> implementation_needs_rework
---
# Implementation Review (Code Review)
**First, ensure we're up to date:**
```bash
git fetch
git status
```
Confirm and display the current feature branch name.
---
**Then run the code review:**
## Code Review Request
Run this command to get the changes to review:
```bash
git diff --unified=5 --no-prefix main...HEAD -- . ":(exclude)pr_info/.conversations/**"
```
No need to run all checks; do not use pylint warnings. Feel free to further analyse any mentioned files and/or the file structure.
### Focus Areas:
- Logic errors or bugs
- Tests for `__main__` functions should be removed (not needed)
- Unnecessary debug code or print statements
- Code that could break existing functionality
- Compliance with existing architecture principles, see `docs/architecture/ARCHITECTURE.md`
### Output Format:
1. **Summary** - What changed (1-2 sentences)
2. **Critical Issues** - Must fix before merging
3. **Suggestions** - Nice to have improvements
4. **Good** - What works well
Do not perform any action. Just present the code review.
