Prilizer: stop rereading every pull request

说明与用途

Prilizer 是一个本地工具，跟踪单个贡献者的最多三个 pull request，使用 Qwen3 识别请求并在明确确认前保持可见。它减少了重复阅读 PR 的需求，但存在推理延迟问题。

问题

Reviewers often reread pull requests after a new commit, wasting time when the request has already been addressed or the thread has moved on.

结果

After refining the pipeline with source‑role and fresh‑confirmation constraints, the tool achieved 12/12 correct outcomes on synthetic cases, eliminating false "Waiting" results and invalid action quotes. However, model inference times ranged from 8.4 to 47.1 seconds, exceeding the 30‑second target.

工作流

• 1. Pull request data (body, comments, reviews, inline comments) is fetched locally.
• 2. Qwen3 1.7B processes the data to propose structured requests.
• 3. Application validates quotes, provenance, actor roles, and freshness.
• 4. Validated requests are persisted independently of the next model summary.
• 5. The digest shows outstanding requests; users can mark as reviewed, dismiss locally, or confirm source.
• 6. If the model fails or data is partial, the card displays "Check manually" and retains older evidence.
• 7. Refreshes are manual; unchanged analyses are cached to avoid re‑analysis.

证据

Prilizer is a local catch‑up desk for up to three public pull requests by one contributor.

来源

The piece I care about most is what happens on the next refresh. An outstanding request stays visible even if the next summary omits it.

来源

The first frozen evaluation failed: 8/12 correct outcomes, including one false Waiting.

来源

The revised pipeline scored 12/12, with zero false Waiting results and zero invalid action quotes.

来源

Fresh‑set model calls took 8.4–47.1 seconds. A real Docker CLI PR took 47.3 seconds, then reused its analysis on an unchanged refresh.

来源