arch-review

Review code changes for architectural consistency and security risks, then create GitHub issues.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/ximing/spark --skill arch-review-ximing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arch-review
Source: https://github.com/ximing/spark/tree/main/.claude/skills/arch.review
Command: npx skills add https://github.com/ximing/spark --skill arch-review-ximing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for high-confidence, actionable code reviews, ensuring architectural consistency, functional correctness, maintainability, and security.

Core Features & Use Cases

  • Architectural Consistency Check: Verifies code adheres to repository constraints and layering.
  • Functional Correctness: Assesses if system functionalities operate as expected.
  • Maintainability Analysis: Identifies redundant code and potential long-term risks.
  • Security Auditing: Detects permission issues, cross-tenant access, and authorization flaws.
  • Automated Issue Creation: Generates GitHub issues for identified problems with detailed evidence.
  • Use Case: When a developer submits a pull request, this Skill can automatically review the changes for architectural compliance, potential bugs, and security vulnerabilities, creating detailed GitHub issues for any findings.

Quick Start

Use the arch-review skill to review the latest code changes for architectural consistency and security vulnerabilities.

Frequently Asked Questions about arch-review

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

FAQPage Schema
How do I automate code review for architectural consistency and security vulnerabilities?

Automated code review for architectural consistency and security verifies code changes against repository constraints, detects cross-tenant access risks, and creates GitHub issues with detailed evidence. It assesses functional correctness and maintainability by identifying redundant logic.

How can I detect cross-tenant access and permission flaws in a pull request?

Detecting cross-tenant access and permission flaws during pull request review involves analyzing code changes against repository constraints to identify authorization risks. The process generates structured findings and creates GitHub issues containing detailed evidence for actionable remediation.

Does this automated code review require the GitHub CLI to create issues?

Yes, automated code review and issue creation require the GitHub CLI (gh) dependency. The skill uses gh to generate GitHub issues containing detailed evidence for architectural inconsistencies, security vulnerabilities, and redundant logic identified during the pull request analysis.

What is architectural consistency checking and how does it identify redundant logic?

Architectural consistency checking verifies that submitted code adheres to repository constraints and layering rules. It identifies redundant logic by analyzing code changes for maintainability, ensuring system functionalities operate correctly while surfacing potential long-term risks through structured findings.

Can I use this to assess functional correctness and maintainability for large repository changes?

Yes, you can assess functional correctness and maintainability for large repository changes. The review analyzes system functionalities to ensure they operate as expected, identifies redundant code, and checks architectural compliance, generating structured findings for actionable review.