skills.rest
signalbeam-io
signalbeam-ioOFFICIAL
Explore all skills by this author →
GitHub

code-review

Identify security, architecture, and quality issues in code changes against origin/main.

2|Updated Dec 9, 2025
Search Tags:#architecture#security#quality#diff#static-analysis#code-review#pull-request
One-click install
npx skills add https://github.com/signalbeam-io/signalbeam-edge --skill code-review-signalbeam-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/signalbeam-io/signalbeam-edge/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/signalbeam-io/signalbeam-edge --skill code-review-signalbeam-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code changes often introduce security risks, architectural drift, and quality issues that are hard to spot in isolation. This Skill provides a structured, repeatable review process that surfaces critical findings before merging.

Core Features & Use Cases

  • Security-focused checks: Detect injection risks, weak authentication patterns, and data handling concerns across diffs.
  • Architecture & maintainability: Identify architectural violations, single-responsibility breaches, and code smells that hinder future changes.
  • PR-ready reporting: Generate actionable findings with severity levels and recommended fixes suitable for pull requests.

Quick Start

Provide the current branch diff to generate a comprehensive code-review report.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I detect security vulnerabilities in a pull request diff?▼

Code review for pull requests works by comparing your current feature branch against origin/main to identify architectural violations and code smells. It outputs a structured report with prioritized findings, risk classifications, and recommended fixes to inform the merge process.

Can I identify architectural drift and code smells in feature branches?▼

You can identify architectural drift and code smells in feature branches by analyzing the diff against origin/main. The review process detects single-responsibility breaches and maintainability issues that hinder future changes, providing actionable findings suitable for pull requests.

What is the best way to automate OWASP checks on a code diff?▼

The best way to automate OWASP checks on a code diff is to process the branch comparison against origin/main. This surfaces injection risks, weak authentication patterns, and data handling concerns across the changes, generating a PR-ready report with severity levels.

Does static analysis for code review work without integrating external dependencies?▼

Static analysis for code review works without external dependencies by evaluating the provided diff directly. It compares the current branch to origin/main to output risk classifications and recommended fixes, operating independently to inform PR reviews.

How do I generate a PR-ready report with risk classifications for code changes?▼

To generate a PR-ready report with risk classifications for code changes, compare your current branch against origin/main. The resulting structured report includes prioritized findings, severity levels, and recommended fixes for security, architecture, and quality issues.

Related Skills

Explore More Software Engineering Skills→
doodledooddoodledood
4

review-agents-md-adherence

Detect AGENTS.md guideline violations in PR code changes.

Community
Intermediate
istinataFTSistinataFTS
2

caveman-review

Generate concise single-line code review comments with severity levels.

Community
Intermediate
ApothecaryManApothecaryMan

react-doctor

Scan React codebases for security, performance, correctness, and architecture issues.

Community
Intermediate
MuhamadAnangMuhamadAnang

code-review-expert

Analyzes git diffs for SOLID violations, security risks, and performance issues.

Community
Advanced