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/severity.md

View on GitHub
# Severity

Severity says how bad the problem is. Whether a finding can block is decided by evidence (see evidence-ladder.md), not by the model's confidence.

| Severity | Definition | Examples |
|---|---|---|
| P0 | Data loss or corruption, security hole, crash or startup failure, irreversible migration error, widespread 5xx, billing error. Use P0 only when the problem holds without assumptions about the input. | A background worker reused the request's context after the request ended; the context was cancelled, the worker panicked, and its recover handler crashed the process. A delete endpoint took the owner id from the request body, so any user could delete another user's files. |
| P1 | User-visible regression on a main path, broken contract with another component, error or retry semantics changed so that work hangs, existing capability removed without replacement. | A notification call was changed to `await` to satisfy a lint rule, so saving a form waited for the email provider to answer. After a model was removed from the catalog, every scheduled job that named it failed instead of falling back to the default. A default flag silently changed from true to false, against the design record. |
| P2 | Edge-case bug, maintainability risk with a concrete failure path, a fix without a regression test where a testable seam exists. | A handler loaded every row of a table and then ignored the result. A flex child without `min-w-0` let a long project name push the dialog out of the sidebar. |
| P3 | Style and naming. | Do not report. |

Rules:
- Main path versus edge case: when a whole class of valid inputs fails (every plugin of one kind, every request through one entry point, every user on one platform), that is a main-path regression for that feature, so P1. An edge case is an unusual value of an input that otherwise works: empty, huge, concurrent, malformed.
- A problem the PR did not introduce or expose is `pre_existing`; it never blocks this PR.
- If two readings of the same problem disagree on severity, report the lower one and explain the condition for the higher one.
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