Stakeholder review for GitHub prototypes · Coming soon
You built a prototype.
Now untangle the feedback.
The prototype is on GitHub. The feedback is in Slack screenshots. Crit gives your team a review link where stakeholders can pin a note to the element they mean — with GitHub Issues behind it.
Coming soon. Review creation isn’t available yet. GitHub login will be required to view and comment.
crit.team/r/…Review previewYour next project
A small idea, ready for a second pair of eyes.
1The problem isn’t getting feedback
It’s finding what the feedback is about.
You share a prototype. Someone posts a cropped screenshot. Someone else replies “this one?” Three threads later, you’re reconstructing a conversation instead of improving the UI.
- 01 / Lost context
“Move this” isn’t a location.
A screenshot in Slack captures pixels, not the element. Which button? Which state? By the time you open the prototype, the useful part of the note is missing.
- 02 / Another review workspace
A throwaway prototype shouldn’t need new seats.
A separate review tool can mean another account, another invitation, another bill. You wanted a quick critique — not a new workspace to administer.
- 03 / A broken trail
The prototype moves on. The thread doesn’t.
The next deploy changes the layout. A new link replaces the old one. The comments still exist, but their context doesn’t travel with them. Now “did we fix this?” needs another meeting.
Put the note where the question starts: on the UI. Keep the work where the team already works: GitHub.
Why Crit, not another feedback thread?
Slack is where the conversation happens. Crit is designed to keep the note attached to what’s being reviewed.
Considering BugHerd, Pastel, or Vercel Comments? Crit’s focus is narrower: GitHub prototypes, a Crit-minted review URL, GitHub identity, and comments stored as Issues. No second review-tool identity for stakeholders.
How mint works
Paste a GitHub link.
Share a review link.
Comments stay on the page.
The planned phase-1 flow keeps the handoff simple:
Sign in. Paste your prototype link.
The builder signs in with GitHub and pastes an in-org GitHub prototype link.
Crit mints the stakeholder URL.
Share a link shaped like
crit.team/r/…. It opens a Crit-hosted preview of the prototype — not the raw GitHub Pages URL.Open. Sign in. Pin.
Stakeholders open that Crit link and sign in with GitHub to view the review. Press c, then click an element to pin a comment.
Keep the comment with the work.
Comments persist as GitHub Issues and stay pinned on the review page, so feedback isn’t only a message in a thread.
Close the loop, without losing the note.
Change · Question · Bug · Works
Mark what kind of feedback it is, right on the element. A question and a bug shouldn’t look like the same task.
Planned, not shipped: Finish-review export for an agent handoff. It is not part of the available product today.
GitHub-gated by design
A share link isn’t an open door.
Stakeholders must sign in with GitHub to see the Crit review — and to comment. The Crit URL is the review destination; it is not an anyone-with-the-link public preview.
GitHub identity for the people. GitHub Issues for the comments. A Crit-hosted preview for the conversation around the UI.
This describes the planned phase-1 experience. Authentication and review creation are not live yet.
Who it’s for
Teams moving from “look at this” to “change this.”
- Builders sharing in-org GitHub prototypes before the next iteration.
- Stakeholders with GitHub accounts who need to point to a specific element, not describe its coordinates.
- Teams already working in Issues who want critique to land alongside the work.
Coming soon to crit.team
Less “which button?”
More useful feedback.
Start with a GitHub prototype. Give stakeholders a Crit review link. Keep their comments on the page.
Review creation is not available yet. No GitHub sign-in or live review is connected on this page.
Prefer a launch note?
Waitlist signup will open here when it’s connected.
crit.team is owned. Site/DNS may still be propagating. Product coming soon; GitHub login will be required to view and comment.