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/team-principles.md

View on GitHub
# Review principles

Apply these in every lens. A concrete violation in the diff is a finding; a debatable design choice goes to `needs_human`.

1. No model special-casing. Budgets, thresholds and behavior must not branch on a model name; parameterize instead.
2. Do not block operations the user triggers by hand. Protection logic belongs on automatic paths only.
3. Fix bad values at the boundary where they are read (fill a default there) instead of adding a policy at every entry point. A fix that touches more than about 10 source files suggests the boundary is wrong: raise it in `needs_human`.
4. Fold fixes into existing mechanisms and keep them stateless: no special branch for one incident, no state carried across calls.
5. Degrade instead of throwing: on unexpected input fall back to a safe default and leave a trace. Throw only when continuing would corrupt data or weaken security.
6. A bug fix comes with a test that fails on the old code and passes on the new code. If there is no seam to test, the PR should say so.
7. Fallback safety checks only need to handle normal usage. A bypass that requires deliberate construction is documented as a threat model, not blocked.
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: 197kUpdated 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