bug-detecter

Diagnose Better Auth OAuth 2.1 PKCE login misconfigurations via static analysis.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/ayeshakhalid192007-dev/humanoid-ai-studio --skill bug-detecter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-detecter
Source: https://github.com/ayeshakhalid192007-dev/humanoid-ai-studio/tree/main/.claude/skills/bug-detecter
Command: npx skills add https://github.com/ayeshakhalid192007-dev/humanoid-ai-studio --skill bug-detecter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Detects bugs in Better Auth + OAuth 2.1 PKCE login flows. Use this skill when the user reports login failures, "page not found" on auth routes, sign-up/sign-in not working, token issues, or CORS/session errors in a Better Auth + Docusaurus + FastAPI stack. Runs a static analysis script and matches symptoms against a curated bug reference.

Core Features & Use Cases

  • Static analysis of key auth/frontend/backend files (auth.js/ts, docusaurus.config.js, AuthContext.tsx, oauth.ts/js, .env) to surface common login bugs.
  • Cross-reference the bug reference in references/better-auth-login-bugs.md to guide exact fixes for symptoms.
  • Stepwise workflow with a deterministic script (scripts/detect_login_bugs.py) to scan a monorepo and report actionable findings.

Quick Start

Run the static analysis script to detect login bugs in a Better Auth + OAuth PKCE stack.

Frequently Asked Questions about bug-detecter

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

FAQPage Schema
How do I debug Better Auth OAuth PKCE login failures in a monorepo?

Debug Better Auth OAuth PKCE login failures by running a static analysis script that scans auth.js, docusaurus.config.js, and backend files to surface misconfigurations like redirect_uri mismatches and PKCE verifier storage issues.

Why does my Better Auth login return page not found on Docusaurus auth routes?

Better Auth login returns page not found when the loginPage URL is misconfigured in Docusaurus. Static analysis detects incorrect route setups and cross-references symptoms against a curated bug reference to guide exact fixes.

Can I use static analysis to detect CORS and session errors in a Better Auth stack?

You can use static analysis to detect CORS and session errors in a Better Auth stack by scanning key frontend and backend files including .env, oauth.ts, and AuthContext.tsx to surface common configuration pitfalls.

What's the best way to fix redirect_uri mismatches in Better Auth OAuth 2.1 flows?

Fix redirect_uri mismatches in Better Auth OAuth 2.1 flows by matching reported symptoms against a curated bug reference. This approach identifies exact configuration discrepancies between Docusaurus frontend and FastAPI backend endpoints.

Does the Better Auth bug detection script work with a FastAPI backend?

The Better Auth bug detection script works with a FastAPI backend. It performs static analysis on monorepos using Better Auth with Docusaurus frontend and FastAPI backend to diagnose PKCE verifier storage and onboarding issues.

When should I not use static analysis for Better Auth login bug detection?

You should not use static analysis for Better Auth login bug detection when diagnosing runtime-specific issues like network latency or dynamic token expiration, because the script relies on scanning static configuration files and a curated bug reference.