review-gitcode-pr

Reviewing a GitCode pull request with evidence requires fetching PR metadata and diffs via oh-gc, then validating each changed file against local repository context to produce anchored, submission-ready findings.

Hunk evidence anchoring works by collecting remote PR diff and view data via oh-gc, then validating each changed file against local repository context to ensure findings are accurately mapped to specific lines.

Before deep code inspection on a GitCode PR, you need the oh-gc dependency and python3 installed, plus a local repository clone to provide the local context required for validating changed files.

You can draft submission comments for a GitCode pull request review by generating a structured output of findings, which the skill prepares for comment submission only after explicit user confirmation.

The best way to ensure every changed file in a PR is reviewed is by applying a required deep-review checklist that assigns an explicit status like reviewed, mechanical-low-risk, or skipped-with-reason to each file, preventing early stops.

A pull request review may stop early if it lacks deep-review checklist enforcement, which this skill solves by requiring an explicit reviewed, mechanical-low-risk, or skipped-with-reason status for every single changed file before completing.