review

Analyze staged changes, commits, or pull requests for code issues.

14|6|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/tyevans/tackline --skill review-tyevans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/tyevans/tackline/tree/main/skills/workflows/review
Command: npx skills add https://github.com/tyevans/tackline --skill review-tyevans

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates and structures the code review process, ensuring code quality, security, and adherence to architectural standards before merging or committing.

Core Features & Use Cases

  • Structured Review: Evaluates code across correctness, security, style, architecture, and testing.
  • Automated Scope Determination: Intelligently parses staged changes, commits, ranges, or PRs.
  • Use Case: After an agent implements a new feature, run /review to get a detailed breakdown of potential issues, ensuring the code is production-ready.

Quick Start

Run the review skill on staged changes to assess code quality.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review for staged git changes and pull requests?

Automate code review by analyzing staged git changes, commits, or pull requests to evaluate correctness, security, style, architecture, and testing. This generates a detailed report categorizing findings by severity with actionable next steps.

Can I run a security audit on a specific commit range?

Yes, you can run a security audit on a specific commit range. The tool intelligently parses commit ranges to identify security vulnerabilities and categorizes findings by severity within a structured code review report.

Does the code review assistant require gh to analyze pull requests?

Yes, gh is required as a dependency to analyze pull requests. The code review assistant uses it to parse pull request targets and evaluate code across correctness, security, style, architecture, and testing dimensions.

What is the best way to ensure code quality before merging a pull request?

The best way to ensure code quality is to run a structured code review assessing correctness, security, style, architecture, and testing. This identifies potential issues and provides a verdict with actionable next steps before merging.

How does automated testing evaluation work during a code review?

Automated testing evaluation works by analyzing staged changes or pull requests to assess test coverage and quality. It categorizes testing gaps by severity and includes actionable next steps in the final code review report.