tdr-review

Review staged and unstaged Git changes with parallel reviewer agents.

Updated Oct 15, 2024
One-click install
npx skills add https://github.com/codemonkey800/lilnas --skill tdr-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdr-review
Source: https://github.com/codemonkey800/lilnas/tree/main/.agents/skills/tdr-review
Command: npx skills add https://github.com/codemonkey800/lilnas --skill tdr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates a comprehensive code review process, acting as a senior staff software engineer, to analyze Git changes and identify potential issues.

Core Features & Use Cases

  • Parallel Code Review: Reviews staged and unstaged Git changes using multiple specialized agents simultaneously.
  • Project Documentation Analysis: Considers the type of software being reviewed to select appropriate reviewer agents.
  • Structured Report Generation: Provides a consolidated report with severity-sorted action items for fixes.
  • Use Case: Utilize the tdr-review skill by typing /review to initiate a code review process.

Quick Start

Initiate a code review by typing /review in the command line.

Frequently Asked Questions about tdr-review

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

FAQPage Schema
How do I automate code review for my staged and unstaged Git changes?

You can automate code review by running a command that acts as a senior software engineer to analyze Git changes. It reviews staged and unstaged files using specialized agents and generates a report with action items.

What is parallel multi-agent code review and how does it work?

Parallel multi-agent code review uses multiple specialized agents to analyze software changes simultaneously. It considers project documentation to select appropriate agents and produces a consolidated report with severity-sorted action items.

How do I generate a structured code review report from Git changes?

To generate a structured code review report, initiate a review of your Git changes. The process analyzes project documentation and executes concurrent reviewer agents to provide a consolidated report with severity-sorted action items for fixes.

Does the code review process analyze project documentation for context?

Yes, the code review process analyzes project documentation to understand the context of the software being reviewed. This ensures the specialized reviewer agents are selected appropriately for a comprehensive analysis.

Can I use parallel processing to review software changes across my entire project?

Yes, parallel processing is used to review software changes by executing specialized reviewer agents concurrently. This allows the system to analyze staged and unstaged Git files efficiently and generate a detailed report.

What is the best way to identify potential issues in Git changes?

The best way to identify potential issues in Git changes is using an automated senior software engineer review process. It analyzes staged and unstaged files and provides a detailed report with severity-sorted action items for fixes.