Review uncommitted code changes by inspecting the working tree and relevant diff. Report likely bugs, regressions, design weaknesses, missing requirements, and validation gaps in severity order, with precise file references and concrete impact.
Review uncommitted code changes
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Inspect the current working tree before making assumptions. Start with git status --short, then read the relevant diff.
Prioritize findings over summaries. Report the highest-impact issues first with precise file references and concrete impact.
Check these areas on every run:
When the user expects action instead of commentary, fix the issues you identify and re-check the result.
When reviewing, keep the response structure tight:
When no issues are found, say so explicitly and still mention residual risks or missing verification.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use this reference to write Aily Block Syntax (ABS), a text format for Blockly scripts. It explains block connections, parameter order, statement inputs, values, and variable references, with examples for conditions, loops, and Arduino program structure.
Implement or modify Blockly/ABS programs using the project’s current board and installed libraries. Check only relevant library evidence, edit the canonical ABS source, sync it to the workspace, and run focused validation when needed.
Plan a new Blockly hardware project by discovering suitable board and library packages, then comparing viable combinations. Each plan outlines wiring assumptions, workspace structure, implementation steps, and validation before the user confirms project creation.
Search indexed chat history to find earlier decisions, tool activity, project summaries, files, and workflow tips. It can also rebuild the local history index when requested or when search results appear out of date.
Create a concise handoff document in the operating system’s temporary directory so another agent can continue the work. It summarizes the conversation, suggests relevant skills, references existing artifacts, and redacts sensitive information.
Survey a codebase and turn verified improvement opportunities into prioritized, self-contained implementation plans for another agent. It can assess bugs, security, performance, tests, technical debt, migrations, tooling, and product direction while keeping source code read-only.