You built a prototype. Now untangle the feedback.

Slack screenshots lose the element. Paste a GitHub Pages URL, get a Crit share link, and get pins that land as Issues — GitHub login to view and comment.

You’ll sign in with GitHub. Reviewers need GitHub login to view and comment. Accepts github.io, github.com/org/repo (→ Pages), and Enterprise Pages (github.company/pages/… or pages.github.company/…).

Comments sit on the UI — question, suggestion, or bug — not in a side thread.

The real problem

Feedback without a place to land.

You share a prototype. Someone pastes a crop. You’re reconstructing the conversation instead of shipping the fix.

  1. 01 — Lost context

    “Move this” isn’t a location.

    Screenshots capture pixels. Crit pins the note to the element.

  2. 02 — Extra tools

    A throwaway prototype shouldn’t need new seats.

    Stakeholders already have GitHub. Crit uses that identity.

  3. 03 — Broken trail

    The UI moves. The Slack thread doesn’t.

    Issues stay with the work, so “did we fix this?” has an answer.

How it works

Paste. Mint. Pin.

  1. Paste your GitHub Pages URL

    Sign in with GitHub and drop in a Pages URL from your org.

  2. Share the Crit link Crit mints for you

    Something like api.crit.team/r/… — a Crit-hosted preview, not the raw Pages URL.

  3. Reviewers sign in, pin the element, leave an Issue

    They press c, click an element, and leave a note. It becomes a GitHub Issue.

Built for GitHub teams

A share link isn’t an open door.

GitHub-gated views

Stakeholders must sign in to open the review and to comment.

Issues, not another inbox

Every pin lands where your team already tracks work.