agentleFS
MarcusJellinghausMarcusJellinghaus/mcp-workspace/.claude/skills/implementation_review/SKILL.md

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

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
  1. Very specific:

    Call mcp__mcp-workspace__git with command "fetch" and args ["origin"].

    line 14
  2. Very specific:

    Use mcp__mcp-workspace__git with command "status" to check working directory state.

    line 15
  3. Very specific:

    Use mcp__mcp-workspace__git with command "diff" to get the changes to review.

    line 26
  4. Distinctive:

    No need to run all checks.

    line 28
  5. Distinctive:

    Critical Issues: - Must fix before merging

    line 39
  6. Distinctive:

    Do not perform any action.

    line 43

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.