my-review

Review local changes or GitHub PRs for correctness and cross-service contracts.

4|1|Updated May 31, 2015
One-click install
npx skills add https://github.com/samcdavid/dotfiles --skill my-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: my-review
Source: https://github.com/samcdavid/dotfiles/tree/main/claude/skills/my-review
Command: npx skills add https://github.com/samcdavid/dotfiles --skill my-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Rigorous OSS-style code reviews that assess local changes or GitHub PRs for correctness, enforce cross-service contracts, validate idempotency, ensure test fidelity, and consider performance. It deduplicates feedback by against existing review comments and researches the codebase to verify findings.

Core Features & Use Cases

  • Persona-driven lenses (Backend, Frontend, Security, Architect, PM, Ops, Quality) to prioritize what is scrutinized.
  • PR and Local Diff coverage: review changes whether they're on a PR or in the working tree.
  • Comment deduplication: avoid re-flagging previously noted issues.
  • Codebase research: deep analysis to verify findings across the codebase.
  • Structured review output: provides a traceable, actionable report.

Quick Start

Choose a review persona and provide either the PR URL/number or your local changes to begin the review.

Frequently Asked Questions about my-review

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

FAQPage Schema
How do I perform an OSS-style code review on a GitHub PR?

Perform an OSS-style code review on a GitHub PR by providing the PR URL or number to apply rigorously assess correctness, cross-service contracts, idempotency, and test fidelity while de-duplicating existing review comments.

Can I review local uncommitted changes instead of a pull request?

Review local changes directly by providing your working tree diff, enabling the same rigorous analysis of correctness, performance, and test fidelity without requiring a formal GitHub pull request.

How do I prioritize different aspects like security or performance during a code review?

Prioritize specific review aspects like security, performance, or quality assurance by selecting a persona-driven lens such as Backend, Frontend, Security, Architect, PM, Ops, or Quality to guide what is scrutinized and how findings are ranked.

What is the best way to avoid re-flagging issues that were already noted in a pull request?

Avoid re-flagging previously noted issues by de-duplicating feedback against existing review comments, ensuring the analysis only surfaces new findings verified through deep codebase research.

Does the code review provide a structured report mapping changes to requirements?

The code review provides a structured, traceable report that maps local changes or PR modifications directly to review requirements, ensuring actionable output and safe, repeatable assessments.

How does codebase research verify findings during a code review?

Codebase research verifies findings during a code review by analyzing the surrounding code structure to ensure cross-service contracts and idempotency checks are accurate before generating a structured report.