// Use this skill whenever MCPMate work needs code review, PR readiness checks, severity calibration, or final findings ordering. Trigger on review requests, merge-readiness checks, PR cleanup, risk discussion, or any request to assess whether a change is ready to land.
Use this skill for MCPMate UI/UX review, UAT planning, Playwright acceptance, Admin Console acceptance, Board acceptance, Extension delivery acceptance, or any request to judge whether a page, flow, component, PR, or deliverable conforms to MCPMate product taste and acceptance standards. Use it even when the user does not say "UAT" if the task involves visual quality, interaction quality, acceptance criteria, release readiness, or product-facing workflow validation.
Use this skill whenever work needs to be aligned with the MCPMate GitHub Project, including roadmap slicing, draft-item planning, PR scoping, worktree setup, or task-status updates. Trigger on requests about planning, roadmap, project board, task center, worktree discipline, or how to split work into reviewable slices.
Use this skill whenever MCPMate work needs test, lint, build, Inspector, or release-slice verification. Trigger on implementation, review, bug fixes, PR preparation, regression checks, or any request to validate backend, frontend, desktop, or MCP behavior before reporting completion.
| name | review-flow |
| description | Use this skill whenever MCPMate work needs code review, PR readiness checks, severity calibration, or final findings ordering. Trigger on review requests, merge-readiness checks, PR cleanup, risk discussion, or any request to assess whether a change is ready to land. |
Use this skill to keep reviews concise, severity-driven, and aligned with repository rules.
references/review-rubric.md when the review needs the full decision and reporting rubric.validation skill when a finding depends on missing or weak validation evidence.