self-review

Run a self-review on your local changes by asking for a review of the current diff. The Skill defaults to git diff HEAD, which captures all staged and unstaged changes, then returns a structured markdown review grouped by file with severity labels.

Specify the base branch when requesting the review, and the Skill uses git diff main..HEAD or origin/main..HEAD to scope the comparison. It reads the full changed files for context, not just the diff, before producing findings.

The review starts with a verdict (Approved, Approved with suggestions, or Changes requested), then groups numbered findings by file. Each finding has a severity label such as Bug, Suggestion, Nit, Security, or Design, plus a code snippet and a concrete fix suggestion.

Yes, a dedicated security pass examines the diff for unvalidated input, injection risks, exposed secrets, missing auth checks, unsafe use of user-controlled data, session handling, and database query safety.

Yes, when you ask to review only staged changes, the Skill scopes the diff with git diff --cached. It also supports specific commit ranges using git diff <from>..<to> when you provide explicit refs.

Yes, staged spec files are audited against Playwright conventions such as accessible locators, hydration-aware navigation, and try/finally cleanup. If no specs are staged, it assesses whether changed routes or server functions need new E2E tests and suggests concrete cases.