nit-vs-blocker-classifier

Classify draft PR-review comments into nit, suggestion, question, issue, or blocker tiers.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/FrogAi/Xenopus --skill nit-vs-blocker-classifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nit-vs-blocker-classifier
Source: https://github.com/FrogAi/Xenopus/tree/main/Gemini/Skills/Gemini%203.1%20Pro/nit-vs-blocker-classifier
Command: npx skills add https://github.com/FrogAi/Xenopus --skill nit-vs-blocker-classifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classify draft PR-review comments into tiers — nit / suggestion / question / issue / blocker — with category + actionability. Prefix each with the team's convention (Conventional Comments / Google nit: / Microsoft / custom). Remove comments that should self-fix before ship. Flag harsh tone. Power-dynamics aware (senior→junior softens; junior→senior concretizes evidence). Read-only — never posts; produces classified list for user to copy-paste or file-level review.

Core Features & Use Cases

  • Classification with tiering and prefixing per Conventional Comments, Google nit, Microsoft styles, or custom conventions.
  • Tone analysis and power-dynamics-aware labeling to guide reviewer communication.
  • Read-only processing that outputs a structured list for user review or export.

Quick Start

Submit a draft list of comments and run the skill to generate a labeled, prefixed review.

Frequently Asked Questions about nit-vs-blocker-classifier

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify PR review comments into nits, suggestions, and blockers?

Classify draft PR-review comments into nit, suggestion, question, issue, or blocker tiers by applying prefix conventions like Conventional Comments or Google nit styles. The tool outputs a structured, prefixed list without posting changes.

What is power-dynamics-aware labeling in code review?

Power-dynamics-aware labeling adjusts review tone based on hierarchy: senior-to-junior comments are softened, while junior-to-senior comments require concretized evidence. This ensures constructive communication during tier classification.

How do I add conventional comment prefixes to draft code review feedback?

Add conventional comment prefixes by processing draft feedback through the classifier. It supports Conventional Comments, Google nit, Microsoft, or custom conventions, generating a prefixed, structured list for manual copy-pasting.

Does the nit vs blocker classifier post comments directly to the pull request?

No, the nit vs blocker classifier operates in a strictly read-only mode. It analyzes draft comments and produces a classified list for the user to review and manually post, ensuring it never posts changes directly.

Why should I flag harsh tone in draft PR review comments?

Flagging harsh tone prevents negative interactions during code reviews. The classifier detects aggressive language and applies power-dynamics-aware adjustments to soften senior feedback and guide junior communication effectively.

Can I use custom prefix conventions for tiering code review comments?

Yes, you can use custom prefix conventions for tiering. The classifier supports Conventional Comments, Google nit, Microsoft styles, or custom team conventions to structure draft PR-review feedback accurately.