Guide

How CodeCritic fitsyour workflow

The long version of the home page: flow, surfaces, and what lands in your account after a run - same product story, more room for detail.

Flow

From the code you have to a merge you trust

Boundary in, structured review, clear exit - aligned with the workflow block on the home page.

  • Wire in what you already have

    A snippet for a fast gut check, a file when the whole module matters, or a GitHub repo when context lives across folders. Detection runs in the app - you are not configuring parsers here.

  • One pass that reads like a review

    Findings roll up by severity and theme - not a single blob of text. Each item explains why it matters, points at lines, and often includes a proposed code change when one is appropriate.

  • A handoff you can act on

    You leave with a prioritized view of what to fix before merge - and what is already solid. No guessing order, no copying advice out of a chat window.

Surfaces

Where CodeCritic runs

One review engine - different entry points. Pick the surface that matches how you ship.

Web app

Paste, upload, or pull from GitHub - all from your account.

The full review experience in the browser: findings, suggested changes, and line context in one place.

Best for: Quick passes, spikes, and onboarding before you wire up automation.

GitHub Action

Reviews on pull requests, feedback where your team already argues about code.

Install the action on the repo. Each push or PR update can trigger the same review - comments land on the diff.

Best for: Team workflows, protected branches, and merge-ready review threads.

REST API

Call the service from jobs, scripts, or internal tools with your API key.

Create reviews and read results over HTTP - when you need a custom gate, reporting, or a non-GitHub source of truth.

Best for: CI pipelines, bespoke automation, and orgs that do not live only on GitHub.

Output

What a review includes

Names may vary by plan - the intent is always structured feedback you can act on.

Score & summary

A quick read on overall quality plus a short narrative - so you know whether to dig in or ship.

Categories & severity

Issues grouped so you triage security and correctness before polish - not one flat list.

Issues with suggested code

Line references, explanations, and proposed edits when the model can suggest a patch - not vague tips.

Structured layout

Same split-style reading experience as on the home workflow section - scan, then apply.

GitHub

PR path

When the Action is installed, each relevant PR event can trigger a review and post results back on the diff.

PR openedor updated
Eventtriggers run
Reviewsame engine
Commenton thread

Next step

Open an account, run a review, or read the step-by-step help when you need YAML and API detail.