Chrome extension · works on github.com

Vague code reviews end here.

Defect Marker adds one-click #Severity:Type labels to every GitHub PR comment. Reviews become searchable, severity becomes obvious, and nothing slips through.

  • Zero permissions
  • No account
  • 100% local
Live demo
github.com/acme/api/pull/1432
Write a review comment
#Major:Missing The auth header is never validated — reject with 401 before touching the database.
Mark as Defect
SeverityMajorMinorCosmetic
TypeMissingExtraInconsistentImprovement
#Major:Missing ready to submit
CancelAdd review comment
#Major:Missing#Minor:Inconsistent#Cosmetic:Improvement#Major:Risk-prone#Minor:Ambiguous#Cosmetic:Extra#Major:Factually-Incorrect#Minor:Extra
01The problem

Reviews without structure don't scale.

Unlabeled comments can't be searched, sorted, or audited. Six months later, nobody knows what was a blocker and what was a nitpick.

Review without labels
  • “this looks wrong”

    No severity. No category. No follow-up.

  • “nit: clean this up later”

    “Later” never comes.

  • “??”

    Fifteen replies to figure out what it meant.

Review with Defect Marker
  • #Major:Missing

    Auth header never validated — reject with 401.

  • #Minor:Inconsistent

    camelCase everywhere else in this file.

  • #Cosmetic:Improvement

    One-liner with Array.from.

02Features

Everything reviewers need, nothing they don't.

Defect Marker stays out of the way until you need it — then it makes labeling a single, deliberate action.

/01

Smart detection

Finds every comment editor across PR conversations, reviews, replies, and inline diffs — layered discovery survives GitHub's soft navigation and lazy rendering.

/02

One-click pills

No dropdowns. Every Severity and Defect Type is visible at a glance and selected with a single click or the arrow keys. The label is inserted for you.

/03

Submission guard

Submit buttons stay disabled while a defect classification is incomplete or its label was deleted — labels never get lost in long review threads.

/04

Native theming

The panel reads GitHub's own Primer CSS variables, so it matches light, dark, dimmed, and high-contrast themes automatically.

/05

Severity at a glance

Color-coded Major / Minor / Cosmetic tints flow through the pills, the preview chip, and the panel border — triage is obvious for the next reviewer.

/06

Accessible by default

Real form controls, visible focus rings, aria-live validation messages, and full prefers-reduced-motion support.

03How it works

From open PR to labeled defect in seconds.

Four steps. No configuration. Compatible with every GitHub UI variation we've seen.

1

Open a pull request

Defect Marker activates automatically in any GitHub PR comment editor — legacy UI or the new React-based one.

2

Mark as defect

A compact panel sits between the editor and its footer. Tick the checkbox and the pill groups animate open.

3

Pick severity & type

One click each: Major, Minor, or Cosmetic, then Missing, Extra, Risk-prone, and more. The label is prepended for you.

4

Submit with confidence

Submit stays disabled until the label is valid and present. Your team gets searchable, consistent feedback.

04In the wild

The real thing, inside a real PR.

Actual screenshots from a GitHub pull request — the panel waits quietly under the comment box, then expands into one-click pills.

Beforefig. 1
GitHub PR comment box with the collapsed 'Mark as Defect' checkbox added below the editor

A quiet checkbox under every comment box

Open any inline comment on a PR and 'Mark as Defect' is already there — no popups, no setup. Leave it unticked and GitHub behaves exactly as normal.

Afterfig. 2
Expanded Defect Marker panel showing severity and defect type pills with the #Minor:Risk-prone label inserted

Tick it, click two pills, done

Severity and Defect Type expand as color-coded pills. Picking Minor + Risk-prone prepends #Minor:Risk-prone to the comment and shows it in the live preview chip.

05The taxonomy

Three severities. Seven types. One source of truth.

Every defect comment gets a structured #Severity:Type tag — searchable, sortable, and instantly recognizable.

#Majorseverity

Must be fixed before approval.

:Missing:Risk-prone:Factually-Incorrect
#Minorseverity

Should be fixed, but not a blocker.

:Extra:Inconsistent:Ambiguous
#Cosmeticseverity

Style and polish level issues.

:Improvement:Inconsistent:Extra
comment.body
preview
> #Major:Missing This endpoint never validates the auth header — request
should reject with 401 before touching the database.

> #Minor:Inconsistent We're using camelCase elsewhere in this file.

> #Cosmetic:Improvement Could be a one-liner with Array.from.
06FAQ

Answers, before you ask.

Still curious? Open an issue on the repo and we'll get back to you.

Yes. Defect Marker detects both the legacy form-based UI and the redesigned React-based comment editor, writing labels through React-safe text insertion so both UIs honor them.

No. Everything runs locally in your browser. The extension requests zero Chrome permissions — no background worker, no network requests, no storage, no telemetry.

No. The panel is styled entirely with GitHub's own Primer CSS variables, so it follows light, dark, dark-dimmed, and high-contrast themes automatically.

No. Labels are only enforced when you explicitly tick 'Mark as Defect'. Regular comments work exactly as before, and the extension only re-enables buttons it disabled itself.

The defaults match common review conventions (Major / Minor / Cosmetic and seven defect types). Custom presets are on the roadmap.

Free · open source · zero permissions

Install in under 30 seconds.

Add Defect Marker to Chrome and your next review comment ships with a label your whole team can search.