agentsclimarketplace

Godot code reviewer

Skill schmoenraad/godot-gamestudio/plugins/godot-gamestudio/skills/godot-code-reviewer

Build Godot games with a supervised AI team: specialists, independent reviewers, runtime QA, and evidence-gated milestones.

Install
npx -y skills add schmoenraad/godot-gamestudio --skill godot-code-reviewer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Independently review Godot GDScript, C#, scenes, Resources, and gameplay changes for correctness, regressions, architecture risks, engine misuse, save compatibility, and missing tests. Use as the opposing reviewer for gameplay-engineering deliverables.

SKILL.md

0.8 KB, as published. Nobody here has run it

Godot Code Reviewer

Do not edit files and do not read maker reasoning.

  1. Inspect the diff, affected scene/resource contracts, call sites, signals, input, autoloads, and tests.
  2. Prioritize crashes, data loss, broken scenes, behavioral regressions, physics errors, lifecycle mistakes, and missing validation.
  3. Run focused checks when needed to confirm a suspected issue.
  4. Present findings first, ordered by severity, with exact file and line references.
  5. Return approved, changes_requested, or inconclusive; mention residual test gaps when approved.

Gives 0 of the 12 instructions most code review skills give

Counted across 610 of the 674 authors here whose files we hold, read 2026-08-06

  • push back with technical reasoning if wrongin 60 of 610, across 24 files
  • ask for clarification on unclear itemsin 51 of 610, across 16 files
  • fix critical issues immediatelyin 45 of 610, across 29 files
  • implement one item at a timein 45 of 610, across 11 files
  • group findings by severityin 44 of 610, across 43 files
  • verify feedback against the codebasein 42 of 610, across 8 files
  • dispatch a code reviewer subagentin 39 of 610, across 23 files
  • fix important issues before proceedingin 37 of 610, across 22 files
  • test each fix individuallyin 35 of 610, across 7 files
  • reply in github comment threadsin 33 of 610, across 5 files
  • check for security vulnerabilitiesin 31 of 610, across 27 files
  • factualize corrections without over-explainingin 30 of 610, across 2 files

Said here and by no other author read

  • Inspect diffs, call sites, signals, autoloads, and tests
  • Run focused checks to confirm suspected issues
  • Present findings ordered by severity with line references
  • Return approved, changes_requested, or inconclusive
  • Mention residual test gaps when returning approved

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.