code-review

Name: code-review
Availability: InStock
Author: Pubky

Analyze git diffs for architecture compliance, quality, and security issues.

23|5|Updated Apr 10, 2025

Search Tags:#automation #architecture #quality assurance #static analysis #code review #refactoring

Ready to run

npx skills add https://github.com/pubky/pubky-app --skill code-review-pubky

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/pubky/pubky-app/tree/main/.cursor/skills/code-review
Command: npx skills add https://github.com/pubky/pubky-app --skill code-review-pubky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the tedious process of checking code changes against project-specific architecture rules, general quality standards, and simplification opportunities, ensuring consistent code health.

Core Features & Use Cases

Architecture Enforcement: Validates code against layer boundaries and project-specific rules defined in the repository.
Quality & Security Audits: Automatically flags hardcoded secrets, error handling gaps, and type safety issues.
Simplification Analysis: Identifies over-abstractions and suggests the use of existing project utilities to keep the codebase clean.

Quick Start

Initiate the code review process by asking the assistant to review your local uncommitted changes.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I automate code review for uncommitted git diffs?▼

You can automate code review for uncommitted git diffs by initiating the review process, which triggers parallel sub-agents to check architecture compliance, general quality, and simplification opportunities against your project configuration files.

What is architecture compliance validation in automated code quality audits?▼

Architecture compliance validation in automated code quality audits is the process of verifying code changes against layer boundaries and project-specific rules defined in the repository. It operates on git diffs to ensure consistent code health and architectural integrity.

Do I need project configuration files to perform static analysis on source code?▼

Yes, project configuration files are required to perform static analysis on source code. The review process needs access to these configurations to verify project-specific rules, detect security vulnerabilities, and provide verified, actionable feedback on maintainability.

Can static analysis detect hardcoded secrets and error handling gaps?▼

Yes, static analysis can detect hardcoded secrets and error handling gaps during quality and security audits. The automated review process flags these vulnerabilities alongside type safety issues to ensure comprehensive code health and maintainability.

What's the best way to identify over-abstractions and code simplification opportunities?▼

The best way to identify over-abstractions and simplification opportunities is through dedicated simplification analysis sub-agents. These agents analyze git diffs to suggest using existing project utilities, keeping the codebase clean and maintainable.

What are the limitations of automated multi-perspective code reviews?▼

Automated multi-perspective code reviews require access to project configuration files and source code to function properly. Without proper configuration files defining project-specific rules, the review process cannot verify architecture compliance or provide verified, actionable feedback.