This is a PR preprocessing step designed to run before your main code review, ideally with a cheaper model like Haiku to save costs in CI. It categorizes file changes, detects what frameworks and languages are in play, flags surface level issues like `any` types or magic numbers, and determines which reference docs your actual reviewer will need. The incremental mode is clever: it reads `.pr-review-state.json` from previous runs and only rechecks files that changed since the last review, carrying over issues from untouched files. Everything gets dumped into `.pr-triage.json` for the next phase to consume. If you're running automated reviews in CI and want to optimize token usage, this gives you a lightweight triage pass before the heavy lifting.
npx skills add https://github.com/xtone/ai_development_tools --skill pr-triage