MiniMax-AI/mcode-stack / stacks/jiachen/skills/pr-review
pr-review
VerifiedReview 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.3 KB |
| references/evidence-ladder.md | markdown | 675 B |
| references/lenses/behavior.md | markdown | 1.0 KB |
| references/lenses/contracts.md | markdown | 1.2 KB |
| references/lenses/cross-feature.md | markdown | 1.3 KB |
| references/lenses/duplication.md | markdown | 1.8 KB |
| references/lenses/general.md | markdown | 887 B |
| references/lenses/security.md | markdown | 887 B |
| references/repos/example.md | markdown | 1.4 KB |
| references/severity.md | markdown | 2.1 KB |
| references/stacks/go-backend.md | markdown | 4.8 KB |
| references/team-principles.md | markdown | 1.2 KB |
references/repos/example.md
View on GitHub# Repository: example
A made-up repository that shows the format of a repository's notes. A
repository keeps its own notes in `.mcode-review.md` at its root, where CI and
local reviews both read them; a file in this directory is named after the last
segment of the repository's `origin` URL instead. List the failure patterns
that the repository's past fix PRs repaired, one per item, most costly first,
each with the place to look.
1. Session refresh runs in two places: the web client refreshes on a 401 and the
API gateway refreshes before it forwards. A change to one must keep the
other in step, or a user gets logged out once a day.
2. Migrations under `db/migrations/` run before the new binary starts, and the
old binary keeps serving for a few minutes. A migration that renames or drops
a column breaks the old binary; add the new column first and drop the old one
in a later release.
3. The settings page saves the whole settings object. A new field without a
default in `src/settings/defaults.ts` is written back as empty and resets
the value for every user who opens the page.
4. Background exports in `src/jobs/export/` retry on any error. A retry after
the upload succeeded but the status write failed sends the user two emails;
the retry must check the stored status first.
5. Prices are stored in cents and shown in dollars. A new screen or report that
reads the stored value directly shows a hundred times the price.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| 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: 197k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |