skills.rest
vix-4800
vix-4800COMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-review

Identify defects, security issues, and architectural risks in code diffs.

1|Updated Aug 6, 2025
Search Tags:#workflow#testing#architecture#security#diff#code-review
One-click install
npx skills add https://github.com/vix-4800/Workstation --skill code-review-vix-4800
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/vix-4800/Workstation/tree/main/roles/ai-tools/files/agents/skills/code-review
Command: npx skills add https://github.com/vix-4800/Workstation --skill code-review-vix-4800

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps reviewers identify defects, security issues, architectural regressions, and missing tests during code changes.

Core Features & Use Cases

  • Diff-first evaluation of code changes and diffs
  • Structured checklist covering correctness, security, architecture, data access, validation, tests, and migrations
  • Guidance for applying risk-based prioritization and actionable feedback across PRs, branches, and patches.

Quick Start

Provide a pull request diff and ask the AI to review for correctness, security, and architecture using the diff-first workflow.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review a pull request diff for security and architecture risks?▼

Use a diff-first review workflow to evaluate pull request diffs against a structured checklist covering correctness, security, architecture, data access, validation, tests, migrations, and style to identify defects and architectural risks.

What is a diff-first code review workflow?▼

A diff-first code review workflow is a structured process that evaluates code changes directly, applying risk-based prioritization to identify defects, security issues, and architectural regressions across pull requests, staged diffs, and patches.

Can I use a structured checklist to review staged diffs and recent branch changes?▼

Yes, you can apply a structured checklist to review staged diffs and recent branch changes, evaluating criteria like correctness, security, architecture, data access, validation, tests, migrations, and style to generate actionable feedback.

What is the best way to identify missing tests and defects in post-implementation patches?▼

The best way to identify missing tests and defects in post-implementation patches is to apply a diff-first evaluation that checks code changes against criteria for correctness, tests, and validation to ensure software integrity.

Does this code review approach work for infrastructure and data-access changes?▼

Yes, this code review approach works for infrastructure and data-access changes by applying a structured checklist that evaluates correctness, security, architecture, data access, validation, tests, migrations, and style across the diff.

Related Skills

Explore More Software Engineering Skills→
nillenille

Code Review

Review code diffs for correctness, security, and conventions.

Community
Advanced
SebKaySebKay
1

review-code

Review code changes for correctness, regressions, maintainability, and test coverage.

Community
Intermediate
0xUrsanomics0xUrsanomics
2

code-review

Review scripts and infrastructure for security vulnerabilities and correctness issues.

Community
Advanced
LayerDynamicsLayerDynamics

diff-review

Review current git diff changes for bugs, security issues, and style inconsistencies.

Community
Intermediate