All Articles
Blog

Spec Reviewer: Bringing Figma and Jira Context into Every Pull Request

By embedding design and product understanding directly into review, Baz removes an entire layer of back-and-forth between design, engineering, and QA.

Nov 8, 2025
Shachar Azriel
Tables of content

Design-to-code alignment has become the hidden cost center of front-end development. Even teams with strong design systems and component libraries spend enormous time syncing what’s in Figma, what’s in Jira, and what’s actually implemented.

When intent isn’t captured early, every review becomes a guessing game. That’s not a workflow problem. It’s a validation problem.

As the VP of Product, I have time each week set aside to review code implementation. It looks like this:

  • Open Figma to check the latest design spec
  • Open Jira to re-read the ticket and acceptance criteria
  • Open a staging link to test the new feature
  • Compare all three manually to see if what shipped matches what was intended

I’ve just spent hours doing design QA manually, matching colors, juggling multiple tabs next to a staging build - sound familiar?

Code review can tell you what’s changed and flag a missing prop but not exactly if it matches what was intended or breaks a core design pattern. Developers can’t validate against design and product intent when those sources live in other tools.

That’s why Spec Reviewer became a key milestone on the Baz code review milestone, and we’re excited that it’s now available. By embedding design and product understanding directly into review, Baz removes an entire layer of back-and-forth between design, engineering, and QA.

Introducing Spec Reviewer: Design-Aware Code Review

Spec Reviewer brings design and issue context directly into the pull request, turning each review into a real validation step, not just a diff check.

Here’s what it does:

  • Connects design and code: Baz links to Figma via MCP to compare visual components, spacing, and hierarchy against the intended design.
  • Understands intent: It pulls in Jira issues to interpret the user story and acceptance criteria.
  • Reviews with context: When you open a PR, Baz analyzes the implementation against those references and surfaces any mismatches.
  • Delivers results where you work: Findings appear as concise, visual comments right inside GitHub, with linked visuals and deeper context available in Baz.

Using Baz in your Github environment you’ll see comments that give guidance to where the code misses the intent

Turn Design Intent into Review Intelligence

Spec Reviewer is designed for the developers who live at the intersection of design and code, and product teams who want faster QA without sacrificing fidelity.

Spec Reviewer is the first step in Baz’s broader vision of intelligent validation. It brings product intent into the review process, and soon, with the upcoming CLI and Checkout, that validation will extend all the way into local and staging environments. The coding loop will finally close, from design to code to runtime.

Spec Reviewer is available today in GitHub for Baz customers.

Connect your Figma and Jira projects and see how much smoother your next review feels.

Meet your new code review agents