signal-review

Identify code issues and output one-line severity-tagged reports.

10|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/mattbaconz/signal --skill signal-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signal-review
Source: https://github.com/mattbaconz/signal/tree/main/gemini-signal/skills/signal-review
Command: npx skills add https://github.com/mattbaconz/signal --skill signal-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a concise, structured code review format that enforces severity levels and a deterministic output, reducing review time and increasing clarity.

Core Features & Use Cases

  • One-line per issue output format: {file}:{line}|{issue}|{severity}|{fix}
  • Enforces mandatory severity per issue and a summary line
  • Useful for code review workflows, PR checks, and automated CI feedback

Quick Start

Review a code diff and generate a structured one-line-per-issue report.

Frequently Asked Questions about signal-review

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

FAQPage Schema
How do I format pull request code reviews to show severity levels?

To format pull request code reviews with severity levels, this skill outputs each issue on a single line using the structure {file}:{line}|{issue}|{severity}|{fix}, enforcing a mandatory severity scale and a concluding summary line for deterministic results.

What is the best way to generate deterministic output for automated code review?

The best way to generate deterministic output for automated code review is to use a structured, one-line-per-issue format. This ensures consistent results across CI feedback workflows by applying a defined severity scale and a summary line to each code target.

Can I review a diff or code block without providing a full repository?

Yes, you can review a diff or code block without a full repository. The skill accepts various targets such as individual files, code blocks, diffs, or PR URLs, identifying issues and outputting them in the structured one-line format.

How do I parse diff reviews into a structured format for CI pipelines?

To parse diff reviews into a structured format for CI pipelines, the skill processes the diff and outputs each identified issue on its own line as {file}:{line}|{issue}|{severity}|{fix}, providing deterministic, machine-readable results.

Does this code review skill require any dependencies to run?

No, this code review skill does not require any dependencies to run. It operates independently to identify issues in your code target and apply the severity-driven, one-line output format without external components.