reviewer

Review git commit diffs for quality, security, and pattern adherence.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/tim-hub/role-based-skills --skill reviewer-tim-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewer
Source: https://github.com/tim-hub/role-based-skills/tree/main/reviewer
Command: npx skills add https://github.com/tim-hub/role-based-skills --skill reviewer-tim-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The reviewer Skill helps developers and maintainers quickly assess code changes for quality, security, and consistency with existing codebase patterns by automating the process of gathering diffs, reading surrounding context, and producing a prioritized challenge report.

Core Features & Use Cases

  • Commit range resolution: Accepts one or two commit hashes or defaults to the latest commit range to determine which changes to inspect.
  • Context-aware analysis: Collects git diffs, commit messages, and full file contents to evaluate pattern adherence, naming, imports, error handling, and potential vulnerabilities.
  • Challenger-style reporting: Produces a structured, prioritized report (critical → low) that cites specific files, lines, and failure/attack scenarios and includes an added Pattern Adherence dimension for codebase consistency.

Quick Start

Review the most recent commit range and produce a challenger-style code review report.

Frequently Asked Questions about reviewer

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

FAQPage Schema
How do I automate code review from git commit history?

Automating code review from git commit history involves resolving a commit range, reading git diffs and logs, and loading full file context. It produces a prioritized challenger-style report citing files, lines, and risk dimensions like security vulnerabilities.

What is a challenger-style code review report?

A challenger-style code review report is a structured, prioritized assessment ranging from critical to low risk. It cites specific files, lines, and failure or attack scenarios, evaluating code quality, security vulnerabilities, and pattern adherence.

How do I review git diffs for security vulnerabilities and code quality?

Reviewing git diffs for security and code quality requires loading full file context for modified files alongside the diff. This enables thorough analysis of naming, imports, error handling, and potential vulnerabilities against existing codebase patterns.

Can I review a specific commit range or just the latest commit?

You can review a specific commit range, not just the latest commit. The process accepts one or two commit hashes to define the inspection scope, or defaults to the HEAD~1..HEAD range when evaluating recent code changes.

Does automated code review check for consistency with existing codebase patterns?

Automated code review does check for consistency with existing codebase patterns. It includes a Pattern Adherence dimension that evaluates whether new changes follow established naming, imports, and error handling conventions within the codebase.