aiperf-code-review

Compare current branch to origin/main and document code-quality gaps with runtime evidence.

526|145|Updated Apr 16, 2025
One-click install
npx skills add https://github.com/ai-dynamo/aiperf --skill aiperf-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiperf-code-review
Source: https://github.com/ai-dynamo/aiperf/tree/main/.agents/skills/aiperf-code-review
Command: npx skills add https://github.com/ai-dynamo/aiperf --skill aiperf-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews the current branch against origin/main, captures findings, validates against the actual code, reproduces issues with the in-repo mock server, and drafts inline GitHub PR review comments anchored to specific files and lines. This living document is updated as work progresses and artifacts are preserved under artifacts/.

Core Features & Use Cases

  • End-to-end branch comparison against origin/main to surface issues
  • Reproducible validation against the in-repo mock server
  • Auto-generates and anchors PR review comments with exact file paths and line numbers
  • Maintains living artifacts under artifacts/ to support traceability

Quick Start

Run the aiperf code-review tool on the current branch to generate living artifacts and inline PR comments.

Frequently Asked Questions about aiperf-code-review

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

FAQPage Schema
How do I automate code review for a GitHub branch against origin/main?

Automated code review against origin/main identifies code-quality gaps, validates findings against the actual codebase, and drafts inline GitHub PR comments anchored to exact files and lines.

What is the best way to reproduce code review issues found during a branch comparison?

Reproducing code review issues uses the in-repo mock server to validate findings and capture runtime evidence, preserving the output as structured artifacts for full traceability.

Can I auto-generate inline PR comments with exact file paths and line numbers?

Auto-generating inline PR comments anchors structured findings to specific file paths and line numbers, summarizing issues with severity levels and source-level evidence.

How do I maintain traceable artifacts during an end-to-end branch comparison?

Maintaining traceable artifacts stores runtime evidence and structured findings under the artifacts directory, creating a living document that updates as branch work progresses.

Does this code review tool work without external dependencies?

This code review tool operates with no external dependencies, relying solely on the in-repo mock server to reproduce issues and validate findings against the current codebase.