angular-pr-complexity

Analyze a git merge commit to produce a PR complexity scorecard.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill angular-pr-complexity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: angular-pr-complexity
Source: https://github.com/ryan-mahoney/ryan-llm-skills/tree/main/skills/angular-pr-complexity
Command: npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill angular-pr-complexity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes a git merge commit to produce a PR complexity scorecard.

Core Features & Use Cases

  • Calculates size, spread, and cognitive load metrics from diff data for Angular/Nx monorepos.
  • Generates a structured PR complexity scorecard to guide code reviews and release risk assessment.
  • Use Case: When evaluating a PR, run this skill to quickly quantify impact and architecture risk.

Quick Start

Provide a merge commit hash to generate the PR complexity scorecard.

Frequently Asked Questions about angular-pr-complexity

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

FAQPage Schema
How do I measure PR complexity for an Angular Nx monorepo?

Measure PR complexity by analyzing a git merge commit diff to calculate size, spread, and cognitive load metrics. The skill produces a structured scorecard that quantifies impact across libraries and apps in an Angular Nx monorepo.

What metrics are used to quantify code review risk in Angular pull requests?

Code review risk is quantified using metrics derived from diff data, per-file change counts, and path-based classifications. The scorecard evaluates size, spread, file-type breakdown, and risk signals to gauge cognitive load.

Can I evaluate TypeScript and SCSS diff impact across multiple libraries in Nx?

Yes, you can evaluate TypeScript and SCSS diff impact across multiple Nx libraries. The skill scopes PR changes across HTML, SCSS, TypeScript, and spec files to quantify spread and risk signals.

How do I generate a PR complexity scorecard from a merge commit hash?

Generate a PR complexity scorecard by providing a git merge commit hash. The skill processes the diff data and per-file change counts to produce a structured report detailing architecture risk and cognitive load.

Does this PR complexity analyzer work without Nx monorepo path structures?

The analyzer relies on path-based classifications specific to Angular and Nx monorepos to evaluate changes across libraries and apps. It requires diff data and per-file change counts structured within this monorepo context.