Skip to content

MiniMax-AI/mcode-stack / stacks/jiachen/skills/pr-review

pr-review

Verified

Review a pull request or the current branch with the MCode Review rules (severity, evidence ladder, lens checklists, review principles) and the repository's own .mcode-review.json and .mcode-review.md. Works with GitHub pull requests and GitLab merge requests. Use when the MCode Review CI pipeline starts a review pass, or when a developer asks to review their PR or branch before asking a person to review it.

references/lenses/duplication.md

View on GitHub
# Lens: duplication and simplification

Occam's razor in both directions: do not duplicate what exists, and do not add abstraction nobody needs.

Check, using the duplication hints in the prompt and your own searches (`git grep`):
- The diff adds parsing, classification, validation or counting logic that the repository already implements. Name the existing implementation with path:line.
- The same diff contains two implementations of one decision (for example a capability check written twice with different fields).
- One of several parallel implementations (DOM menu and native menu, send and resume, proxy path and direct path) is changed and the others are not, with no explanation.
- A fix that repeats an earlier fix found elsewhere in the repository instead of reusing it.

Severity follows the evidence:
- Copies that already disagree and cause wrong behavior are a bug: report it with the failure path and rate it with severity.md. When the copies disagree on a whole class of valid inputs, it is P1 (example: a package list shows every plugin of one kind as installable while the installer rejects them).
- A new copy that still agrees with the existing one is P2: suggest reusing the existing implementation by path:line.
- Reuse only along allowed dependencies. Before suggesting an import, check the direction: when the existing implementation lives in a layer or module the caller must not depend on (a lower layer importing an upper one, one service importing another service's internals, see the repository's boundary rules), a local copy is acceptable. Report it only when the copies already disagree, and then suggest moving the rule down into a module both may use.
- When no implementation exists yet, do not suggest creating a shared layer for two or three similar lines.
- Report one finding per duplicated decision and list every copy in the body.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall