code-reviewer

Automate code reviews with backend and frontend convention checks.

Updated Feb 9, 2026

Search Tags:#performance #security #beads #review #conventions #static-analysis #code-review

Ready to run

npx skills add https://github.com/msanssouci/opencode --skill code-reviewer-msanssouci

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/msanssouci/opencode/tree/main/skills/code-reviewer
Command: npx skills add https://github.com/msanssouci/opencode --skill code-reviewer-msanssouci

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires beads-workflow, and includes references (resource) components.

What problem does it solve?

Code review specialists ensure consistent, high-quality reviews that enforce clean code, DRY principles, and project conventions, reducing defects and security risks across teams.

Core Features & Use Cases

Automated, project-wide code quality checks aligned to backend and frontend conventions
Actionable feedback with prioritized fixes and guardrails for security and performance
Beads-driven review workflow: generate or attach fix tasks to beads tasks when issues are found

Quick Start

Prompt the reviewer to assess the latest beads task and return a structured critique with suggested fixes.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema

How do I automate code reviews to enforce security and performance conventions?▼

To automate code reviews, prompt the reviewer to assess the latest beads task and apply project conventions, security, and performance checks. It returns a structured critique with suggested fixes and generates or attaches fix tasks to beads workflows when issues are found.

What is a beads-driven code review workflow?▼

A beads-driven code review workflow surfaces tasks across backend, frontend, API, and CLI repositories for automated quality checks. It identifies code-quality issues and attaches fix tasks directly to the beads tasks to track resolutions.

Do I need project references to run static analysis checks for code quality?▼

Yes, automated code reviews require references to project conventions, static analysis checks, and testing guidelines. These references provide the guardrails needed to output structured reviews with actionable fixes.

Can I use automated code review for frontend and API repositories?▼

Yes, automated code review applies to tasks across backend, frontend, API, and CLI repositories. It enforces clean code, DRY principles, and project conventions to reduce defects and security risks across these environments.

What's the best way to generate actionable fix tasks during a code review?▼

The best way to generate actionable fix tasks is using a beads-driven review workflow that evaluates code against static analysis checks. When issues are found, it outputs a structured review and attaches fix tasks directly to beads tasks.

Why does my code review workflow need beads-workflow?▼

Code review workflows need beads-workflow to surface tasks across repositories for evaluation. This dependency enables the reviewer to generate or attach fix tasks to beads tasks when code-quality issues are identified.