api-contract-reviewer
Skill3 starsChanged 38 days agoMITView on GitHub
Behavioral review of Playwright API contract tests (specs, clients, fixtures, test data) for patterns that cause false positives, silent contract drift, test coupling, secret leaks, or access through a route the project forbids. Reads the project's `CLAUDE.md` for what is particular about the product. API-only: does not check UI locators, waits, or Page Objects. Trigger: "review this API test", "check this API spec", "is this API test correct", "review API spec", "why is this contract test flaky", "code review API test", "check contract test quality", "anti-patterns in this API spec", any API `.spec.ts` shared without explicit instructions.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- ralvarez-ai/ralvaskillstheir own version, first seen Nov 1, 2026
- ralvarezdev/ralvaskillstheir own version, first seen Sep 29, 2026
- domehahn/skiltheir own version, first seen Jul 28, 2026
- conectlens/lenserfighttheir own version, first seen May 28, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- conectlens/lenserfight★ 18same name
- ralvarez-ai/ralvaskills★ 4same name
- ralvarezdev/ralvaskills★ 4same name
- domehahn/skil★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- api-contract-writerSkill
- e2e-writerSkill
- playwright-sdet-expertSkill
- pw-pom-generatorSkill
- pw-project-bootstrapSkill
- pw-test-reviewSkill
- qa-shift-leftSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
If the user shares a directory, scan every .spec.ts plus the clients and fixtures they import.
- Distinctive: line 29
Read CLAUDE.md in the test folder first ("Project profile" and "Test conventions").
- Very specific: line 48
Walk the catalog: Read references/anti-patterns.md and check each item top-down.
- Distinctive: line 52
Don't fabricate: No finding without a line number and a mechanism.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
API Contract Reviewer
Behavioral review of Playwright API contract tests. Find patterns that cause false positives, silent contract drift, coupling between tests, auth or secret problems, and violations of the project's access rules. Not a style linter: the formatter covers formatting and style.
When this skill applies
- "review this API test / spec", "is this contract test correct / flaky / OK?"
- An API spec shared without instructions
- A PR diff touching API clients, fixtures, or test data
If the user shares a directory, scan every .spec.ts plus the clients and fixtures they import.
Context you need before reviewing
Read CLAUDE.md in the test folder first ("Project profile" and "Test conventions"). It tells
you what this skill cannot know:
- Response shapes: plain JSON, or an envelope where a business failure can be HTTP 200 with a non-success code; where the machine-readable error code lives.
- Auth: which headers or tokens every call needs, and where test accounts come from.
- Access rules: which hosts and routes tests may use, which endpoints must not be called, where mutating tests may run.
- The suite's own conventions (fixtures, data helpers, naming).
No CLAUDE.md: infer these from the fixtures and two existing specs, and say in the report that
the review assumed them. The writer conventions are in the api-contract-writer skill
(references/honest-tests.md, references/optional-layers.md); cite them when a finding depends
on one. Catalog items about envelopes (C2, H2) and forbidden routes (C4) apply only when the
profile describes such a thing: adapt the names in them to this product.
Workflow
- Read the code. Open every file in scope, plus the fixtures and clients it imports.
- Walk the catalog. Read
references/anti-patterns.mdand check each item top-down. Record file path, line number, and snippet. - Write the report using
references/output-template.md. Skip empty sections. One sentence per "why", explaining the mechanism. - Don't fabricate. No finding without a line number and a mechanism. Always include "What's good".
Philosophy
The author is a senior QA engineer. Every finding explains how the pattern breaks at runtime: which false pass, which leak, which flake. Where the product handles money, balances or permissions, treat silent false passes on those as Critical.
References
references/anti-patterns.md— catalog Critical → Low, with mechanism and fixreferences/output-template.md— report structure
Open both at the start of every review.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.