Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

machina-code-reviewer

Estrelas31

Forks24

Atualizado6 de maio de 2026 às 16:47

Use when reviewing Machina pull requests, local diffs, commits, or mailing-list patch series that may inform Machina changes.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

gevico

gevico/machina

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·SOC 15-1253

SKILL.md

readonly

name	machina-code-reviewer
description	Use when reviewing Machina pull requests, local diffs, commits, or mailing-list patch series that may inform Machina changes.
license	MIT

Machina Code Reviewer

Review for behavior, safety, tests, and repository fit before style.

Inputs

GitHub PR: gh pr view <id> --json title,body,files,commits,reviews
Local diff: git diff --stat then git diff
Commit range: git log --oneline <base>..HEAD and git diff <base>...HEAD
Mailing-list series: b4 am <message-id-or-url>

Review Focus

User-visible behavior and regressions.
Unsafe Rust scope and safety comments.
Device-model side effects, reset paths, and memory access width.
Test coverage in tests/, including edge and failure cases.
Documentation updates under docs/ when behavior or interfaces change.
Commit hygiene: small commits, English subject, Signed-off-by only.

Output Format

Lead with findings ordered by severity. Use file and line references when available. Keep summaries short and put them after findings.

Patch-Series Handling

Use b4 am for lore/public-inbox series, inspect the cover letter first, and apply only in an isolated branch or worktree. Do not apply external patches on top of unrelated local changes.

Mais deste repositório

mesmo repositório

machina-build

gevico/machina

Use when building Machina, running cargo check, debugging Rust build failures, or deciding which repository build command to run.

2026-05-0631

machina-code-explorer

gevico/machina

Use when finding Machina definitions, call sites, crate boundaries, device models, target code, or QEMU-inspired subsystem mappings.

2026-05-0631

machina-issue-helper

gevico/machina

Use when summarizing or preparing to debug Machina GitHub issues, bug reports, feature requests, or reproduction notes.

2026-05-0631

machina-qemu-oracle

gevico/machina

Use when comparing Machina behavior with QEMU, using difftest/oracle tooling, or debugging CPU, interrupt, memory, or device-model parity.

2026-05-0631

machina-testing

gevico/machina

Use when choosing, adding, listing, or running Machina tests, including targeted Rust tests and workspace validation.

2026-05-0631

name	machina-code-reviewer
description	Use when reviewing Machina pull requests, local diffs, commits, or mailing-list patch series that may inform Machina changes.
license	MIT

Machina Code Reviewer

Review for behavior, safety, tests, and repository fit before style.

Inputs

GitHub PR: gh pr view <id> --json title,body,files,commits,reviews
Local diff: git diff --stat then git diff
Commit range: git log --oneline <base>..HEAD and git diff <base>...HEAD
Mailing-list series: b4 am <message-id-or-url>

Review Focus

User-visible behavior and regressions.
Unsafe Rust scope and safety comments.
Device-model side effects, reset paths, and memory access width.
Test coverage in tests/, including edge and failure cases.
Documentation updates under docs/ when behavior or interfaces change.
Commit hygiene: small commits, English subject, Signed-off-by only.

Output Format

Lead with findings ordered by severity. Use file and line references when available. Keep summaries short and put them after findings.

Patch-Series Handling

Use b4 am for lore/public-inbox series, inspect the cover letter first, and apply only in an isolated branch or worktree. Do not apply external patches on top of unrelated local changes.