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/lenses/cross-feature.md
View on GitHub# Lens: cross-feature impact
- Shared components, stores and global styles: list the other features that use what the PR changed and check at least the most used ones.
- UI changes: layout regressions are hard to see in code. If the description has no before/after screenshots or recording, raise it in `needs_human`. Check list keys, merge versus replace on refresh, controls that move, flex children without `min-w-0`, magic z-index values.
- Platform: Windows paths and file modes, Electron packaging (asar), macOS-only APIs, terminal versus desktop clients reporting the same identity.
- Background work: new workers, cron jobs, consumers or topics need an owner per lane and per environment; lanes passed from the entry point down.
- Cost, latency and data leaving the machine: a new model call, network call or heavy step on a path that fans out (every sub-agent, every retry, every message) multiplies cost and waiting time; a new outbound destination for conversation or file content is data egress. Ask in `needs_human` for the limit, the progress shown while the user waits, and whether the user is told what is sent where.
- Rolling releases: server and client versions that run side by side; feature flags and their defaults.
- Intended behavior changes: who depends on the old behavior? Ask in `needs_human` when the description does not answer it.
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: 322k | 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: 198k | 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: 119k | 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 |