Proactive Review Workflow

Automates multi-pass code review across Python, TypeScript, Go, and JavaScript files.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/cdalsoniii/brightpath-coder --skill proactive-review-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Proactive Review Workflow
Source: https://github.com/cdalsoniii/brightpath-coder/tree/main/.cursor/skills/proactive-review-workflow
Command: npx skills add https://github.com/cdalsoniii/brightpath-coder --skill proactive-review-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the tedious and time-consuming process of code reviews, ensuring code quality, security, and performance are addressed proactively.

Core Features & Use Cases

  • Multi-dimensional Analysis: Reviews code across quality, security, and performance aspects.
  • Automated Categorization: Classifies findings into blocking issues, suggestions, or minor style points.
  • Post-merge Validation: Verifies the impact of changes after they are merged.
  • Use Case: When a pull request is opened, this Skill automatically analyzes the changes for potential bugs, security vulnerabilities, and performance bottlenecks, providing actionable feedback before merging.

Quick Start

Run proactive review on the current pull request.

Frequently Asked Questions about Proactive Review Workflow

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

FAQPage Schema
How do I automate code review for security and performance on pull requests?

Automated code review for pull requests is achieved by analyzing PR diffs across quality, security, and performance dimensions, categorizing findings by severity, and posting actionable review comments before merging.

Does automated code review work with Python, TypeScript, Go, and JavaScript files?

Automated code review supports Python, TypeScript, Go, and JavaScript files, analyzing pull request changes across these languages to identify potential bugs, security vulnerabilities, and performance bottlenecks.

How do I categorize code review findings into blocking issues and suggestions?

Categorizing code review findings involves automated classification that separates blocking issues from minor style points and suggestions, ensuring developers can prioritize fixes before and after merging.

Can I validate code changes after merging to verify their impact?

Post-merge validation verifies the impact of merged changes by performing automated checks on the source code, ensuring that the integration does not introduce regressions or unexpected behavior.

What access is needed to automate pull request code reviews?

Automating pull request code reviews requires read access to source code and PR diffs for analysis, and write access to publish categorized review comments directly to the pull request.

What is multi-pass code review and when do I need it?

Multi-pass code review is an automated process that sequentially evaluates code across quality, security, and performance dimensions, needed when proactively identifying complex vulnerabilities and bottlenecks in pull requests.