pr-reviewer
idavidov13/agentic-playwrightReviews a Git branch as a pull request against the base branch (auto-resolved from origin/HEAD — usually main or master) using this repo's own rules — the…
Scores out of 100 · grade B+
2026-08-14Works
40% of the score90/100
- References 1 file that is not in the repo: foo.ts.
Maintained
25% of the score100/100
- no commits in the last 12 weeks
- repo is less than two weeks old
Adopted
20% of the score20/100
- 30 stars on the source repo.
Documented
15% of the score100/100
- 2,595 words with worked examples.
- Ships 4 bundled files.
Install
npx skills add idavidov13/agentic-playwright/pr-reviewerWhat the check found
| Finding | What it means |
|---|---|
| Missing files | It points at files that are not in the repository, so those steps will fail. |
Files it references that are not in the repository
What it says it does
Reviews a Git branch as a pull request against the base branch (auto-resolved from origin/HEAD — usually main or master) using this repo's own rules — the CLAUDE.md constitution and the .claude/skills/ that apply to the changed files. Fetches the branch, switches to it, diffs it against the merge-base, routes the changed files to every applicable skill, verifies (eslint + prettier + tsc, and attempts the affected tests), then reports tiered findings with a confidence score. After reporting it OPTIONALLY offers to implement fixes for the findings, and only if fixes are applied does it ask permission to commit. Use this whenever the user names a branch alongside any review intent — "review PR for branch X", "PR review on aex-1234-foo against master", "review the diffs on branch Y", "check / audit the changes on branch Z", "is branch W good to merge". Use it even when the user says "PR" without the word "review", or "review" without "PR", as long as a branch is in play. Do NOT use this for reviewing the current uncommitted working-tree diff (that is /code-review's job) or for authoring brand-new tests/page objects from scratch (route to common-tasks / api-testing / page-objects instead).
Also in idavidov13/agentic-playwright
| Artifact | Score | What the check found | Type | Reach | Last commit |
|---|---|---|---|---|---|
| data-strategyidavidov13/agentic-playwright | clean | Skill | 30 stars | today | |
| debuggingidavidov13/agentic-playwright | clean | Skill | 30 stars | today | |
| refactor-valuesidavidov13/agentic-playwright | clean | Skill | 30 stars | today | |
| selectorsidavidov13/agentic-playwright | clean | Skill | 30 stars | today | |
| test-standardsidavidov13/agentic-playwright | clean | Skill | 30 stars | today | |
| ai-native-workflowidavidov13/agentic-playwright | clean | Skill | 30 stars | today |
Other code review skills
Browse all| Artifact | Score | What the check found | Category | Reach | Last commit |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowers | clean | Code review | 173,412 installs | 2 days ago | |
| scaffold-exercisesmattpocock/skills | clean | Code review | 241,781 installs | today | |
| financial-statementsanthropics/knowledge-work-plugins | clean | Code review | 3,719 installs | today | |
| review-contractanthropics/knowledge-work-plugins | clean | Code review | 3,017 installs | today | |
| backport-prvercel/next.js | clean | Code review | 142k stars | today | |
| create-prvercel/next.js | clean | Code review | 142k stars | today |
Put this measurement in your README
A badge carrying how many listings this index holds from the repository and how many pass every static structural check. It reads from this index every time somebody loads your page, so it changes when the measurement changes and there is nothing to keep up to date. Free, no account, and the value is not something you or we can set by hand.
[](https://skillworks.kynth.studio/?q=idavidov13%2Fagentic-playwright)Would rather not hotlink us? Every badge is also served in shields.io’s endpoint schema, so shields renders the image and your readers never talk to our domain:
Published by Toolproof, the masthead over this index and eight others. The method behind the number is at toolproof.kynth.studio/methodology, and the whole thing is readable as JSON with no key at /api.
