review
Installation
SKILL.md
Review a Docling pull request
Use these steps for every review. Human reviewers can use the same steps. Explain the affected contract so that a reviewer need not know Docling internals. Read AGENTS.md and load other applicable task routes. For document conversion without repository changes, use the package usage skill.
1. Fix the review scope
Read the live PR description, diff, reviews, and CI results. Record the base and head commit IDs. Use an isolated worktree; preserve other changes and staging. For a re-review, read each open finding and the author's response.
Exit: The changed files and affected contracts are known. The reviewed head is exact, and prior findings are listed for verification.