UiPath Solution & Artifact Reviewer

Review UiPath solutions and artifacts for structural validity, quality, best practices, optimization, correctness, and business alignment. Produce a structured review report with findings and recommendations.

When to Use

Use for requests to review, audit, check, evaluate, improve, quality-gate, or understand the business value or architecture of a UiPath project, solution, or artifact; artifact-type best-practice reviews; and inheritance of an existing solution.

Critical Rules

1. Read-only. Never manually modify files. The sole exceptions are the CLI-owned writes of an agent review, uip agent refresh and uip agent review-history add (agent-review-guide.md); run them by default and never restore or clean up what they change. If the user explicitly forbids any change to the project — ruling out every write, CLI-owned included ("make no changes of any kind") — the user's instruction wins: do not run them, and list them under Rules Skipped. An instruction scoped to editing ("do not manually edit files", "read-only review") does NOT cover these CLI-owned writes: run both. Report fixes and route them to uipath-rpa, uipath-agents, uipath-maestro-flow, uipath-maestro-bpmn, uipath-api-workflow, uipath-coded-apps, uipath-platform, or uipath-solution.
2. Validate first. Every RPA entry point requires uip rpa validate, plus a project-level uip rpa build — build compiles the whole project, including entry points validate was never pointed at, so a clean per-file validate can still fail build. Use uip maestro flow validate, uip maestro bpmn validate, and uip api-workflow validate as applicable. Every CLI validation command uses --output json. Report each command's Error, Warning, and Info counts; detail every Error and Warning, but add no detail lines for clean results. A review without both RPA validate and build is incomplete.
3. Discover and classify every project before reviewing any project.
4. Classify findings as Critical (blocks deployment), Warning (should fix), or Info (improvement opportunity).
5. Establish or infer business context before optimization; queues and additional components are not automatically better.
6. Do not duplicate validation findings. Reference the output rule ID and message rather than restating checks or passes. Counts include all results; Errors and Warnings also receive detail lines.
7. Limit analysis to 30 minutes. For solutions with 10+ projects, provide a summary and deep dives for the three highest-risk projects, offering the remainder separately.
8. Agent projects follow agent-review-guide.md. Once Step 1 classifies a project as Agent (Low-Code) or Agent (Coded), read that guide and run its Critical Rules and Steps 2–6 for that project; the steps below apply to it only where the guide points back to them.
9. Put intended but unapplied rules in Rules Skipped, including missing tooling/files, unavailable review CLI, and status: deferred. Do not list non-applicable rules.