Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingtai-ai/dev-guide-pr-review-deliverables
Nested lingtai-dev-guide reference for getting a PR review-ready: PR readiness gates, multi-model/daemon/Claude read-only review passes, self-contained local HTML explainers, PR body hygiene and gh pr edit troubleshooting, source-labeled deliverables with syntax/validation checks, and maintainer authorization boundaries for opening, editing, and merging PRs.
Passed 13 of 18 test cases with the skill, and 2 of 18 without it.
and 17 more in the full report
13 fixed3 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
In my branch, I renamed src/core/router.py to src/routing/engine.py. ANATOMY.md references the old path. Should I update ANATOMY.md in a follow-up PR after this code change lands?
| Checked | Without skill | With skill |
|---|---|---|
| The response requires updating ANATOMY.md in the exact same commit as the file move or rename. | Missed | Passed |
The instructions your model reads when the skill loads.
Nested lingtai-dev-guide reference. Read this after the top-level router sends you here to prepare a PR for review, build its human-facing explainer, and run review gates before asking for a merge.
It consolidates the PR-review-gate, HTML-explainer, deliverable-template, and release-style-audit practices, covering preparing and reviewing PRs and their human deliverables. Release publication is outside this bundled guide — use the dedicated release owner available in the maintainer's environment.
A PR is review-ready only when (1) the diff is clean and validated, (2) a self-contained HTML explainer tells the human the story, and (3) the change has passed at least one independent review pass. Opening, editing, and merging PRs are external side effects: do them only after an explicit maintainer authorization for that side effect.
git diff --check (no trailing whitespace / conflict markers).ANATOMY.md is updated in the same commit.Known repo pitfalls: docs/stars/stars.csv may use CRLF intentionally — do not
"normalize" it; and portal tests may need frontend assets built first
(npm --prefix portal/web run build).
Run at least one independent, read-only review pass before merge. Strongest first:
test cases passed, vs 2 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.