mr-milchick

Orchestrate Git-based code review and cleanup across recent commits or the current branch.

Updated May 11, 2026
One-click install
npx skills add https://github.com/ruimfernandes/claude --skill mr-milchick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mr-milchick
Source: https://github.com/ruimfernandes/claude/tree/main/skills/mr-milchick
Command: npx skills add https://github.com/ruimfernandes/claude --skill mr-milchick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mr. Milchick helps you safely wrap up implementation work by automatically reviewing recent or current-branch changes, cleaning up dead code, checking translation usage, and running targeted quality analyses (readability, coverage, flakiness, and performance).

Core Features & Use Cases

  • Scope-based code review orchestration: review the last N commits or the current branch since the mainline divergence (merge-base).
  • Deterministic cleanup first: formats Elixir files and removes confidently unused dead code in the changed set before deeper analysis.
  • Quality review team: runs parallel specialists for readability, test coverage gaps, flaky tests in modified/created tests, and performance risks.

Quick Start

Trigger it by telling your AI: "Mr. Milchick, review my last 5 commits and proceed to the cleanup."

Frequently Asked Questions about mr-milchick

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review for recent git commits?

Automating code review for recent git commits involves parsing commit counts, collecting diffs, and dispatching targeted analyses for readability, coverage, flakiness, and performance. This Skill orchestrates that entire workflow by reviewing the last N commits or current-branch changes against a resolved mainline base.

What is the best way to clean up dead code before analyzing a branch diff?

Cleaning up dead code before analyzing a branch diff requires a deterministic formatting and removal step applied to the changed file set. This Skill formats Elixir files and removes confidently unused dead code before dispatching deeper quality and performance reviews.

Can I detect flaky tests in modified files after a merge?

Detecting flaky tests in modified files after a merge is possible by running specialized reviewers on the changed set. This Skill runs parallel specialists to check modified or created tests for flakiness as part of its post-merge orchestration.

Does this code review orchestration work with Elixir projects?

Code review orchestration works with Elixir projects by applying deterministic formatting to Elixir files before deeper analysis. It also checks translation usage and removes unused dead code specifically within the changed Elixir file set.

How do I review the current branch diff against the mainline base?

Reviewing the current branch diff against the mainline base requires resolving the merge-base and collecting the divergent changes. This Skill automates that scope resolution, runs a cleanup phase, and then applies specialized reviewers for performance risks and coverage gaps.

Why should I run cleanup before checking test coverage and performance risks?

Running cleanup before checking test coverage and performance risks ensures that dead code and formatting inconsistencies do not skew the deeper analysis. This Skill mandates a deterministic cleanup phase first so that readability, coverage, and performance reviews operate on a clean diff.