reviewing-code

Reviews code diffs line-by-line using a four-layer heuristic and a repo-local review ledger.

3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/OktayCopurlu/ai-shared --skill reviewing-code-oktaycopurlu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewing-code
Source: https://github.com/OktayCopurlu/ai-shared/tree/main/.github/workflows/skills/reviewing-code
Command: npx skills add https://github.com/OktayCopurlu/ai-shared --skill reviewing-code-oktaycopurlu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often degrade into superficial LGTM approvals based on diff summaries, missing bugs, test coverage gaps, and architecture drift hidden inside changed hunks. ## Core Features & Use Cases - Changed Hunk Inspection: Reads every changed hunk with surrounding context and classifies each as OK, finding, question, or unnecessary, recording actionable items in a repo-local review ledger. - Four-Layer Heuristic: Applies surface correctness checks, test coverage gap analysis, bounded refactor signals, and architecture attention questions, with file-type lenses for templates, scripts, composables, tests, styles, and config. - Adaptive Depth and Modes: Scales review depth by diff size and switches between review-only mode for PRs and self-review mode for local changes. - Use Case: Before opening a PR on a 250-line feature branch, run a self-review to catch a missing error-state test, an unnecessary wrapper in a Vue template, and a cross-domain import, all reported with exact file and line references. ## Quick Start Ask the assistant to review this PR or review my staged changes line-by-line and report findings with file and line references.

Frequently Asked Questions about reviewing-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request line-by-line with an AI assistant?▼

Provide the PR URL or number and ask for a review. The skill fetches the diff, inspects every changed hunk with surrounding context, and reports findings ordered by severity with exact file and line references in PR comment format.

How to self-review code changes before creating a PR?▼

Run the skill against your staged or unstaged local changes to trigger self-review mode. It reports findings and proposed fixes first without editing code, then waits for your explicit instruction before applying anything.

Does this code review approach run tests or linters?▼

No, the review reads the diff and existing CI status instead of re-running gates. Lint, type-check, and test suites are treated as separate gates that already ran, so the review focuses on issues those tools cannot catch.

What file types does the code review cover?▼

It applies dedicated lenses to templates and markup, component scripts, composables and utilities, tests, CSS and SCSS, and config or type files. Vue single-file components get separate template, script, and style passes.

How does the review handle very large pull requests?▼

Diff size determines depth: under 50 lines gets a single pass, 200-499 lines get a deep file-by-file review, and 500+ lines trigger a warning that the PR is too large for full-confidence review, with lower-confidence areas stated explicitly.

What is the review ledger and where is it stored?▼

The ledger is a scratch markdown file created at tmp/code-review-<timestamp>.md inside the repository being reviewed. It records only actionable findings, questions, and unnecessary changes, is never committed, and is linked in the final review response.