Back to skills directory

GraphQL Schema Review

New

Reviews nullability, N+1, auth boundaries and breaking changes when looking at a schema PR.

GraphQL Schema Review is an Agent skill for Development. Reviews nullability, N+1, auth boundaries and breaking changes when looking at a schema PR. Tags: GraphQL · schema · 评审 · API.

DevelopmentAuthor: 编辑整理Visit

What is GraphQL Schema Review

GraphQL Schema Review packages a Development workflow for agents. Reviews nullability, N+1, auth boundaries and breaking changes when looking at a schema PR.

Install GraphQL Schema Review in Cursor / Claude / Codex

Claude Code Install with the command on this page, or place the skill in ~/.claude/skills or project .claude/skills so Claude can detect GraphQL Schema Review.

Cursor After the install command writes the skill directory, invoke GraphQL Schema Review by name in the Cursor agent.

Codex Install into the Codex skills directory and call it by name. If only a generic command is listed, run it locally and confirm Codex can see the skill.

This page has no install command. Check the project home for how to install GraphQL Schema Review.

Please visit the Project Home to see installation and usage instructions.

How to Use

Claude Code: Place the skill in ~/.claude/skills (personal) or the project .claude/skills directory, and Claude will auto-detect it.

Cursor / Windsurf: After installing via npx skillsadd, the skill directory is placed in the configured path.

Codex CLI: After installation it loads automatically from the skills directory and is invoked by name.

Tags

GraphQLschema评审API

Similar recommendations

FAQ

What is GraphQL Schema Review for?

GraphQL Schema Review is a Development skill. Reviews nullability, N+1, auth boundaries and breaking changes when looking at a schema PR.

Can Claude, Cursor, and Codex all use GraphQL Schema Review?

Yes if the client supports Agent Skills and has loaded the skill directory. Check the project home for compatibility notes.

What similar skills exist?

Related items come from the same Development group so you can pick a closer workflow.