skills.rest
maronnjapan
maronnjapanCOMMUNITY
Explore all skills by this author →
GitHub

pkce-reviewer

Review PKCE test cases against OAuth 2.1 requirements for compliance gaps.

Updated Aug 27, 2026
Search Tags:#oauth#compliance#security-testing#pkce#oauth2.1#code_verifier#code_challenge
One-click install
npx skills add https://github.com/maronnjapan/maronn-openid-provider --skill pkce-reviewer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pkce-reviewer
Source: https://github.com/maronnjapan/maronn-openid-provider/tree/main/.claude/skills/pkce-reviewer
Command: npx skills add https://github.com/maronnjapan/maronn-openid-provider --skill pkce-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews PKCE test coverage to ensure PKCE implementations meet OAuth 2.1 requirements, identifying gaps and ensuring mandatory aspects are tested across authorization and token flows.

Core Features & Use Cases

  • Review PKCE test targets across code_verifier validation, code_challenge validation, and S256 transformation.
  • Verify alignment with OAuth 2.1 sections 4.1.1, 4.1.3, 7.5.1, and 7.5.2, and report missing scenarios.
  • Map test coverage to practical use cases and generate actionable remediation recommendations.

Quick Start

Run the reviewer against your PKCE test suite to identify coverage gaps and ensure compliance with OAuth 2.1.

Frequently Asked Questions about pkce-reviewer

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

FAQPage Schema
How do I audit PKCE test coverage for OAuth 2.1 compliance?▼

To audit PKCE test coverage for OAuth 2.1, review your test cases against requirements for code_verifier, code_challenge, S256 transformation, and error handling at authorization and token endpoints.

What are the OAuth 2.1 PKCE requirements for code_verifier validation?▼

OAuth 2.1 PKCE requirements mandate code_verifier validation covering permitted characters, minimum and maximum lengths, high entropy, and mandatory S256 transformation to ensure secure authorization code flows.

How do I find missing PKCE test scenarios in my OAuth 2.1 implementation?▼

Find missing PKCE test scenarios by mapping your test suite against OAuth 2.1 sections 4.1.1, 4.1.3, 7.5.1, and 7.5.2, identifying gaps in code_verifier and code_challenge error handling.

Does OAuth 2.1 require S256 transformation for PKCE code_challenge?▼

Yes, OAuth 2.1 requires mandatory S256 transformation for the PKCE code_challenge, meaning your tests must verify correct implementation of this cryptographic transformation at the authorization endpoint.

Can I check PKCE compliance gaps for both token and authorization endpoints?▼

Yes, you can check PKCE compliance gaps by reviewing test cases for correct handling of code_verifier and code_challenge at both the token and authorization endpoints to ensure full OAuth 2.1 coverage.

Related Skills

Explore More Software Engineering Skills→
AkallabetAkallabet

oauth

Implement OAuth 2.0/2.1 authorization flows with PKCE in Fastify applications.

Community
Advanced
AbdullahMalik17AbdullahMalik17
9

configuring-better-auth

Configure OAuth 2.1 and OIDC authentication with Better Auth and MCP.

Community
Advanced
jpoutrinjpoutrin
14

oauth

Implement OAuth 2.0 and OpenID Connect authorization code flows with PKCE.

Community
Intermediate
Greenmamba29Greenmamba29

github-pr-reviewer

Review GitHub pull requests for code quality and security issues.

Community
Advanced