implementation_review
Skill49 starsChanged 2 days agoMITView on GitHub
Code review of implementation with compact diff analysis
1 other project uses a version of this.
Adopted by
Most recently taken up by
- MarcusJellinghaus/mcp-tools-pyword for word, first seen Aug 31, 2026
Other versions1 project uses a version of this.
Word for word · 1
- MarcusJellinghaus/mcp-tools-py★ 21100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- check_branch_statusSkill
- commit_pushSkill
- discussSkill
- implementation_approveSkill
- implementation_finaliseSkill
- implementation_needs_reworkSkill
- implementation_new_tasksSkill
- implementation_review_supervisorSkill
- implement-directSkill
- issue_analyseSkill
- issue_analyse_supervisorSkill
- issue_approveSkill
- issue_createSkill
- issue_requirementsSkill
- issue_updateSkill
- plan_approveSkill
- plan_reviewSkill
- plan_review_supervisorSkill
- plan_updateSkill
- pr_comment_triageSkill
- rebaseSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Call mcp__mcp-workspace__git with command "fetch" and args ["origin"].
- Very specific: line 15
Use mcp__mcp-workspace__git with command "status" to check working directory state.
- Very specific: line 26
Use mcp__mcp-workspace__git with command "diff" to get the changes to review.
- Distinctive: line 28
No need to run all checks.
- Distinctive: line 39
Critical Issues: - Must fix before merging
- Distinctive: line 43
Do not perform any action.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Implementation Review (Code Review)
First, ensure we're up to date:
Call mcp__mcp-workspace__git with command "fetch" and args ["origin"].
Use mcp__mcp-workspace__git with command "status" to check working directory state.
Call mcp__mcp-workspace__check_branch_status.
Confirm and display the current feature branch name.
Then run the code review:
Code Review Request
Use mcp__mcp-workspace__git with command "diff" to get the changes to review.
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:
- Summary - What changed (1-2 sentences)
- Critical Issues - Must fix before merging
- Suggestions - Nice to have improvements
- Good - What works well
Do not perform any action. Just present the code review.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

