القائمة
Use when reviewing Machina pull requests, local diffs, commits, or mailing-list patch series that may inform Machina changes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| 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 |
Review for behavior, safety, tests, and repository fit before style.
gh pr view <id> --json title,body,files,commits,reviewsgit diff --stat then git diffgit log --oneline <base>..HEAD and git diff <base>...HEADb4 am <message-id-or-url>tests/, including edge and failure cases.docs/ when behavior or interfaces change.Signed-off-by only.Lead with findings ordered by severity. Use file and line references when available. Keep summaries short and put them after findings.
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.
Use when building Machina, running cargo check, debugging Rust build failures, or deciding which repository build command to run.
Use when finding Machina definitions, call sites, crate boundaries, device models, target code, or QEMU-inspired subsystem mappings.
Use when summarizing or preparing to debug Machina GitHub issues, bug reports, feature requests, or reproduction notes.
Use when comparing Machina behavior with QEMU, using difftest/oracle tooling, or debugging CPU, interrupt, memory, or device-model parity.
Use when choosing, adding, listing, or running Machina tests, including targeted Rust tests and workspace validation.