cross-cutting-review

Review PRs and diffs across performance, security, operations, reliability, and data axes.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/foutoucour/guitar-match --skill cross-cutting-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-cutting-review
Source: https://github.com/foutoucour/guitar-match/tree/main/.claude/skills/cross-cutting-review
Command: npx skills add https://github.com/foutoucour/guitar-match --skill cross-cutting-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured framework to assess changes that touch multiple domains (performance, security, operations, reliability, and data), ensuring risk is identified early and actions are clearly categorized.

Core Features & Use Cases

  • Multi-axis assessment of touched areas only
  • Blocking vs advisory classification
  • Generates a concise risk profile for PRs and diffs
  • Use Case: when a change touches auth and logging, review across axes and generate remediation items.

Quick Start

Provide a PR URL or diff and let the reviewer generate a cross-cutting report across all five axes.

Frequently Asked Questions about cross-cutting-review

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

FAQPage Schema
How do I review a pull request that touches multiple domains like security and operations?

Cross-cutting review evaluates PRs and diffs across performance, security, operations, reliability, and data axes. It focuses only on touched areas and generates a risk profile with actionable remediation items.

What is a cross-domain change assessment for code diffs?

A cross-domain change assessment analyzes diffs to identify risks across performance, security, operations, reliability, and data. It classifies findings as blocking or advisory and produces a concise risk profile.

How do I generate a risk profile with blocking and advisory classifications for a PR?

Provide a PR URL or diff to generate a risk profile. The review assesses touched areas and explicitly categorizes actionable items as either blocking or advisory.

Can I use this cross-cutting review for changes that only affect authentication and logging?

Yes, the review applies to changes touching any combination of domains like auth and logging. It assesses only the touched areas and generates remediation items across all relevant axes.

What's the best way to assess operational and reliability risks in a code change set?

Apply a multi-axis change assessment to the change set. It evaluates operational and reliability impacts alongside other domains and outputs a structured risk profile with clear actions.

When do I need a multi-axis review for my code changes?

You need a multi-axis review when a change spans multiple domains and requires early risk identification. It ensures risks across performance, security, operations, reliability, and data are categorized.