conductor-review

Automate code reviews against project guidelines, design specs, and test suites.

51|8|Updated Jan 7, 2026

Search Tags:#git #testing #software engineering #quality assurance #code review #compliance

Ready to run

npx skills add https://github.com/hlhr202/Conductor-for-all --skill conductor-review-hlhr202

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conductor-review
Source: https://github.com/hlhr202/Conductor-for-all/tree/main/.agents/skills/conductor-review
Command: npx skills add https://github.com/hlhr202/Conductor-for-all --skill conductor-review-hlhr202

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the code review process, ensuring that implementations align with project guidelines, design principles, and the original plan, thereby improving code quality and maintainability.

Core Features & Use Cases

Automated Code Review: Analyzes code changes against project standards and guidelines.
Plan Compliance Check: Verifies if the code implements the intended functionality as defined in the track's plan.
Style and Security Audits: Checks for adherence to coding style guides and identifies potential security vulnerabilities.
Test Execution: Automatically runs the test suite to ensure changes haven't introduced regressions.
Use Case: After a developer completes a new feature, this Skill can be invoked to perform a thorough review, identify issues, and suggest fixes before merging.

Quick Start

Use the conductor-review skill to review the current in-progress track.

Frequently Asked Questions about conductor-review

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

FAQPage Schema

How do I automate code review for compliance with project guidelines and design specs?▼

Automated code review analyzes code changes against project standards, design principles, and the original plan to verify implementation correctness and compliance. It checks style adherence, identifies security vulnerabilities, and executes test suites to prevent regressions before merging.

What is the best way to verify code compliance and run test suites automatically?▼

The best way to verify code compliance is using an automated review process that analyzes code changes for correctness, style adherence, and security vulnerabilities while executing the test suite. This ensures implementations align with project guidelines and validates changes prevent regressions.

How does automated code review check for security vulnerabilities and style compliance?▼

Automated code review checks for security vulnerabilities and style compliance by analyzing code changes against established project standards and guidelines. It verifies implementation correctness, identifies potential security flaws, and ensures adherence to coding style guides before suggesting fixes.

Can I use automated code review to verify plan compliance after completing a feature?▼

Yes, you can use automated code review to verify plan compliance after completing a feature. It verifies if the code implements the intended functionality as defined in the track's plan, analyzes correctness, executes test suites, and suggests fixes before merging.

Do I need Git to run automated code reviews on software development tracks?▼

Git is typically required to run automated code reviews on software development tracks because the review process analyzes code changes, verifies implementation against project guidelines, and executes test suites to validate those specific changes before merging.

Why does automated code review execute the test suite during the compliance check?▼

Automated code review executes the test suite during the compliance check to ensure that code changes haven't introduced regressions. It validates the implementation against the original plan and project guidelines while verifying correctness, style compliance, and security vulnerability absence.