code-review

Automate parallel code standards and specification reviews against commit history.

1|Updated Dec 26, 2021
One-click install
npx skills add https://github.com/Zangetsu101/dotfiles --skill code-review-zangetsu101
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Zangetsu101/dotfiles/tree/main/agents/skills/code-review
Command: npx skills add https://github.com/Zangetsu101/dotfiles --skill code-review-zangetsu101

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill unit automates the process of code review, providing a parallel analysis of code standards adherence and specification fulfillment, saving time and improving code quality.

Core Features & Use Cases

  • Parallel Analysis: Conducts Standards and Spec reviews concurrently to provide a comprehensive overview of code quality.
  • Standards Review: Checks for adherence to coding standards and baseline code smells.
  • Spec Review: Ensures that the code meets the requirements specified in the originating issue/PRD/spec.
  • Use Case: Ideal for reviewing branches, pull requests, or work-in-progress changes to ensure they meet both project standards and original specifications.

Quick Start

Execute the code-review skill to initiate a code review for the current branch.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code review for pull requests to check standards and spec adherence?

Automated code review runs parallel standards and spec analysis on your branch to identify deviations from coding standards and compare code against issue tracker requirements. It provides a comprehensive overview of code quality and specification fulfillment.

What is parallel standards and specification analysis in a codebase?

Parallel standards and specification analysis concurrently checks code for adherence to baseline coding standards and validates fulfillment against originating requirements. This concurrent review process identifies deviations and ensures code meets both project standards and original specifications.

Can I review work-in-progress branches against issue tracker documentation?

Yes, code review analyzes work-in-progress branches by comparing commit history against issue tracker and documentation. It ensures work-in-progress changes meet project standards and fulfill the original specifications detailed in the PRD or issue.

Does the code review process require commit history and issue documentation?

Yes, effective code review requires analysis of commit history and comparison against issue tracker and documentation. These inputs enable the parallel review of code standards adherence and specification fulfillment for branches and pull requests.

What is the best way to ensure my code meets both coding standards and PRD specifications?

The best way is to run parallel standards and spec analysis on your branch. This concurrently validates coding standards adherence and specification fulfillment against originating requirements, identifying deviations and code smells for improved quality.

When should I not use automated code review for my changes?

Automated code review is not suitable when commit history, issue tracker data, or specification documentation are unavailable. The parallel analysis requires these inputs to compare code against coding standards and originating requirements accurately.