<PRs.md/>

Guides

Web Dashboard

The web dashboard is the quickest way to create challenges and manage your setup. No install required — just a browser.

Challenges tab

This is the main view after sign-in. If you have an API key saved, a URL input appears at the top. Paste a GitHub PR link (e.g. https://github.com/owner/repo/pull/123) and click Generate.

PRs.md fetches the diff via the GitHub API and sends it to your chosen LLM. Generation typically takes 5–15 seconds depending on the diff size and the provider.

Supported URL formats
  • https://github.com/owner/repo/pull/123
  • https://github.com/owner/repo/pull/123/files

Challenge list

Below the creator, all your past challenges appear in reverse chronological order. Each card shows the PR title, repo, status (pending, passed, or failed), and the date created. Click a card to view the challenge detail or resume a quiz in progress.

Taking the quiz

Once a challenge is ready, click Start Quiz. The timer counts down from 3:00. You must answer all three questions before it reaches zero.

  • Questions are generated from your actual diff — not generic knowledge
  • One question is a hallucination trap (it references something that isn't in the PR)
  • Copy-paste is disabled in the answer boxes during the quiz
  • You have up to 5 attempts per challenge

After submitting, the LLM grades each answer 0–100 and returns written feedback. Your overall score is the average across the three answers.

Proof page and badge

A passing result creates a permanent proof page at /proof/[id]. From there you can copy the Markdown badge snippet and paste it into your PR description:

[![PRs.md Verified](https://prs.md/api/badge/[id])](https://prs.md/proof/[id])

The badge is an SVG served by the app and can be embedded anywhere images are rendered — GitHub PR descriptions, README files, or Notion pages.

Proof pages are public. Anyone with the URL can view your Q&A and score. This is intentional — the whole point is to give reviewers something they can verify.

API Keys tab

Manage your stored API keys here. You can save one key per LLM provider (OpenAI, Anthropic, Gemini). Keys are encrypted with AES-256-GCM before storage and are never returned in plaintext after being saved.

To update a key, delete the existing one and add the new value. To rotate keys, do the same — revoke in your provider dashboard first, then swap here.

Integrations tab

The dashboard also contains setup guides for the CLI, MCP Server, and GitHub Actionintegrations. Each section generates a pre-filled config snippet using your account's MCP token.