review-strict

Reviews current branch or working-tree changes with evidence-based findings and a merge assessment.

1.6k|73|Updated Mar 13, 2025
One-click install
npx skills add https://github.com/UniClipboard/UniClipboard --skill review-strict
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-strict
Source: https://github.com/UniClipboard/UniClipboard/tree/main/.agents/skills/review-strict
Command: npx skills add https://github.com/UniClipboard/UniClipboard --skill review-strict

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often miss subtle regressions, security issues, or cross-platform breakage, and reviewers may edit files or give vague feedback. This Skill performs a strict, read-only review of the current diff and produces concrete, evidence-backed findings ordered by severity.

Core Features & Use Cases

  • Evidence-Based Findings: Every issue cites the exact file and line, the concrete trigger, why it matters, and the smallest sound correction.
  • Prioritized Review Scope: Focuses on correctness, security and privacy (plaintext persistence, sensitive logs, clipboard data exposure), architecture, cross-platform behavior, and missing tests.
  • Merge Assessment: Ends with a clear verdict — ready to merge, merge after fixes, redesign required, or insufficient evidence — without editing, committing, or pushing anything.
  • Use Case: Before merging a pull request that touches clipboard synchronization logic, invoke this Skill to get a senior-level review that flags a plaintext persistence issue at an exact line and recommends the minimal fix.

Quick Start

Ask the AI to use $review-strict to strictly review the current changes on this branch.

Frequently Asked Questions about review-strict

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

FAQPage Schema
How do I get a strict code review of my current changes?

Invoke $review-strict or ask for a strict review of the current branch or working-tree changes. The Skill reviews the diff first, cites exact files and lines for each finding, and ends with a merge readiness verdict without modifying any files.

What kinds of issues does a strict code review check for?

It prioritizes correctness, regressions, concurrency, security and privacy risks like plaintext persistence or sensitive logs, architecture problems such as dead code and hard-coded values, cross-platform behavior, and missing or ineffective tests.

Does the strict review modify or commit my code?

No. The review is strictly read-only. It inspects the diff and necessary surrounding code, reports findings with severity ordering, and explicitly does not edit, commit, or push anything.

How are review findings reported and prioritized?

Each finding cites the file and exact line, states the concrete trigger as input or state leading to incorrect behavior, explains why it matters, and proposes the smallest sound correction. Findings are ordered as blocking, important, or optional.

When should I not rely on this strict review alone?

The review focuses on the current diff and only inspects unchanged code when needed to establish behavior. If evidence is insufficient, it reports a residual verification gap, so runtime testing and CI validation remain necessary.