code-reviewer

Review TypeScript code for anti-patterns, security vulnerabilities, and completeness gaps.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Hashzin-0/Curion --skill code-reviewer-hashzin-0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/Hashzin-0/Curion/tree/main/.opencode/skills/code-reviewer
Command: npx skills add https://github.com/Hashzin-0/Curion --skill code-reviewer-hashzin-0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps ensure generated or authored code meets quality, maintainability, and security expectations by automatically checking for anti-patterns, missing implementations, TypeScript errors, accessibility issues, and potential injections or secrets exposure.

Core Features & Use Cases

  • Comprehensive checks: anti-pattern detection, modularization, maintainability, TypeScript compilation checks, completeness (no placeholders), security scans (XSS, injection, secrets), UI/UX accessibility and responsiveness, performance and compatibility.
  • Actionable reports: outputs machine-readable JSON for CI and human-friendly Markdown reports with file/line specifics and suggested fixes.
  • Integration scenarios: use during PR reviews, CI pipelines, agent-generated code validation, pre-commit gates, or manual user-requested audits.

Quick Start

Run a full review on src/components/UserCard.tsx and return a JSON report plus a Markdown summary listing security, completeness, and TypeScript issues.

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 review for TypeScript compilation errors and security vulnerabilities?

Automated code review detects anti-patterns, TypeScript compilation errors, and security vulnerabilities like XSS or injection by scanning source files, flagging placeholders, and producing structured JSON and Markdown reports with suggested fixes.

Can I run static analysis on agent-generated code to check for completeness gaps?

Yes, static analysis validates agent-generated code by checking for completeness gaps and flagging placeholders to ensure no missing implementations remain before integration into pull requests or CI pipelines.

Does this code review approach work within CI pipelines and pull request workflows?

Yes, this code review approach works within CI pipelines and pull request workflows by outputting machine-readable JSON reports with file and line specifics, serving as pre-commit gates or manual audit triggers.

How do I check frontend components for accessibility and responsiveness issues?

Checking frontend components for accessibility and responsiveness issues involves scanning UI code against established accessibility guidelines, detecting anti-patterns, and generating actionable Markdown reports with specific file references.

What is the best way to scan code for secrets exposure and injection risks?

The best way to scan code for secrets exposure and injection risks is applying security scans during code review that identify potential XSS, injection vectors, and exposed secrets, returning structured JSON reports for CI validation.