code-review

Redirect legacy code-review prompts to the jstar-reviewer workflow.

23|5|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/JStaRFilms/VibeCode-Protocol-Suite --skill code-review-jstarfilms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/JStaRFilms/VibeCode-Protocol-Suite/tree/main/assets/.agent/skills/code-review
Command: npx skills add https://github.com/JStaRFilms/VibeCode-Protocol-Suite --skill code-review-jstarfilms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deprecated compatibility alias for J-Star Reviewer. Use jstar-reviewer for the canonical install, review, audit, and automation flows.

Core Features & Use Cases

  • Redirects legacy code-review prompts to the canonical jstar-reviewer workflow to ensure consistent install, configuration, and execution of review and audit flows.
  • Enables teams to rely on a single, maintained workflow for code review, audit, and automation tasks via a simple alias.
  • Useful in projects that still reference the deprecated code-review skill and require seamless redirection to jstar-reviewer without breaking existing prompts.

Quick Start

Invoke the canonical jstar-reviewer workflow by installing jstar-reviewer and running its review and audit steps.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I redirect deprecated code-review prompts to a canonical workflow?

Redirect deprecated code-review prompts by applying an alias that routes commands to the canonical jstar-reviewer workflow, ensuring consistent install, review, and automation flows without breaking existing project references.

What is backward-compatible code review automation?

Backward-compatible code review automation uses an alias to redirect legacy code-review skill references to a maintained canonical workflow, ensuring consistent execution of review and audit tasks across existing projects.

Do I need to install jstar-reviewer to use the code-review alias?

Yes, installing jstar-reviewer is required because the code-review skill acts solely as a redirect alias, routing prompts to the canonical jstar-reviewer workflow for actual review, audit, and automation execution.

Why does my project still reference the deprecated code-review skill?

Projects reference the deprecated code-review skill from earlier configurations, and this alias ensures those existing prompts seamlessly route to the maintained jstar-reviewer workflow without requiring immediate prompt rewrites.

Can I run headless code review and audit tasks through this alias?

Yes, the alias routes to the canonical jstar-reviewer workflow, which supports running review and audit tasks via chat --headless and --json outputs for automated, consistent code analysis.