super-review:graphql

Detect GraphQL schema and resolver risks including authorization gaps, N+1 patterns, pagination issues, and unsafe error formatting in PR diffs.

Updated May 15, 2026
One-click install
npx skills add https://github.com/mattnowdev/super-review --skill super-review-graphql
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: super-review:graphql
Source: https://github.com/mattnowdev/super-review/tree/main/skills/graphql
Command: npx skills add https://github.com/mattnowdev/super-review --skill super-review-graphql

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GraphQL APIs often ship with subtle denial-of-service, authorization, and correctness weaknesses that linters miss and review comments can easily get wrong without concrete evidence.

Core Features & Use Cases

  • DoS surface review: Detects missing query depth limits, missing query complexity/cost controls, and introspection exposure in production.
  • AuthZ and data-leak prevention: Flags missing field-level authorization, unsafe Federation entity handling, and subscription authorization gaps.
  • Performance and resilience patterns: Catches N+1 resolver patterns, unbounded list fields without pagination, and unsafe error formatting that leaks stack traces or DB details.
  • Protocol hygiene for attackers: Looks for alias abuse bypasses of rate limiting and persisted-query enforcement gaps.

Quick Start

Ask the AI to review a PR that updates GraphQL schema/resolvers for DoS, authorization, pagination, N+1, and error-leak risks with exact quoted evidence from the diff.

Frequently Asked Questions about super-review:graphql

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

FAQPage Schema
How do I review a GraphQL PR for security and authorization issues?

Review a GraphQL PR by evaluating schema and resolver diffs for missing field-level authorization, unsafe Federation entity handling, and subscription authorization gaps to prevent data leaks and access control bypasses.

What are common GraphQL DoS vulnerabilities and how can I detect them in a diff?

Common GraphQL DoS vulnerabilities include missing query depth limits, absent query complexity controls, and introspection exposure in production. You can detect these by analyzing schema diffs for unbounded depth and missing cost analysis configurations.

How do I catch N+1 resolver problems and unbounded list fields in GraphQL?

Catch N+1 resolver problems and unbounded list fields by inspecting resolver implementations for missing DataLoader-driven batching and checking that list fields enforce pagination caps to prevent unbounded data fetching.

Does this GraphQL review approach work with Apollo and Ariadne-style projects?

Yes, the review approach applies when diffs touch GraphQL SDL or resolver implementations, and explicitly supports projects with Apollo or Ariadne-style dependencies to evaluate authorization, performance, and protocol hygiene.

Why does my GraphQL API leak stack traces and database details in errors?

GraphQL APIs leak stack traces and database details due to unsafe error formatting in resolvers. Reviewing error handling logic in the diff ensures sensitive implementation details are filtered from API responses.

What is the best way to enforce persisted queries and prevent alias abuse in GraphQL?

Enforce persisted queries and prevent alias abuse by reviewing GraphQL protocol configurations to identify rate limiting bypasses and gaps in persisted-query enforcement within the API layer.