Fundamental Library for Angular is an SAP-maintained Angular component library implementing SAP's design system and wrapping UI5 Web Components. Angular developers use its typed UI components and higher-level composites to build SAP-style web interfaces. Catalogue entries provide skills, agents, instructions, and a rule for working with the library.
Borrowing it
Nothing to install: this file belongs to SAP/fundamental-ngx. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SAP/fundamental-ngx/main/.claude/skills/review-pr/SKILL.mdgit clone --depth 1 https://github.com/SAP/fundamental-ngxWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sap/fundamental-ngx/review-pr)<a href="https://agentmods.dev/skills/sap/fundamental-ngx/review-pr"><img src="https://agentmods.dev/badge/skills/sap/fundamental-ngx/review-pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sap/fundamental-ngx/review-pr"><img src="https://agentmods.dev/badge/skills/sap/fundamental-ngx/review-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00017 | $0.01304 |
| Opus 5 | $0.00009 | $0.00652 |
| Sonnet 5 | $0.00003 | $0.00261 |
| Haiku 4.5 | $0.00002 | $0.00130 |
Grade A, and why
review-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review: #$0
If $0 is empty or not a number, ask the user for a PR number before proceeding.
Context
Fetch the PR details:
- Diff: !
gh pr diff $0 - PR info: !
gh pr view $0 - Changed files: !
gh pr diff $0 --name-only
Review Checklist
For each changed file, check the applicable sections below. Report findings grouped by severity: Blocking (must fix), Suggestion (should fix), Nit (optional).
1. Angular 22+ Patterns
- New code uses
input()/output()/model()/linkedSignal(). Existing@Input()/@Output()decorators being modified should prefer migration to signal functions, but it's not blocking. -
host: {}in decorator — no@HostBinding()/@HostListener() -
@if/@for/@switch— no*ngIf/*ngFor/*ngSwitch - No
standalone: truein@Component(default since Angular 19) - No
allowSignalWritesoption ineffect()(the option no longer exists) -
DestroyRef+takeUntilDestroyed()— no customDestroyedService -
computed()+host: { '[class]': }— noCssClassBuilder/@applyCssClass - Member ordering: decorated props → signal inputs/outputs → public → protected → private → constructor → methods
2. State Management
-
signal()only used when a reactive consumer exists (template, computed, effect, host binding) - Plain properties for internal bookkeeping, one-time flags, cached values
- No redundant
markForCheck()after signal updates -
BehaviorSubject→signal()where there are no async consumers -
effect()for signal reactions; RxJS only for async operations (HTTP, WebSocket, timers) - No
effect()used for state derivation — usecomputed()orlinkedSignalinstead -
linkedSignalused where mutable derived state is needed (noteffect()+signal.set()) - No object/array mutation in place then
signal.set()with same reference — always new references - No conditional signal reads creating invisible dependency gaps in
effect()/computed()
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 115 lines · 17 tokens per session scan A d74633ee0931
review-pr is a skill published in the GitHub repository SAP/fundamental-ngx (294 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 1,304 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
angular-best-practices
Official Angular v22 coding best practices — signals, standalone, native control flow, zoneless, host bindings, Signal Forms, inject(), and accessibility (WCAG AA / AXE). Use whenever writing, generating, or reviewing Angular/TypeScript code in this repo.
igniteui-angular-linting
Quick-reference for linting the core Ignite UI for Angular library. Covers the combined lint command (lint:lib), ESLint for TypeScript and templates, and Stylelint for Sass/SCSS styles. Use when an agent needs to run the main linters, fix lint errors, or understand the primary lint configuration. Do NOT use for…
logic-component-shape
Decision tree for single component versus container/presenter, which componentStructure to generate, and which componentType to declare. Invoked by logic-placement and logic-review, not directly.
logic-placement
Decide where new logic belongs — component shape, logic layer, and store variant — when designing a component, service, or store in an Angular/Otter workspace. Use logic-review to assess existing code.
logic-review
Review existing components, services, or stores for misplaced logic — presenter leaks, componentType mismatches, wrong store variants. Use logic-placement when designing something new.
logic-state-layer
Decision tree for whether logic belongs in the component class, a service, or an NgRx store, including service scope and where API calls go. Invoked by logic-placement and logic-review, not directly.