code-review

Identify and report issues in code changes and diffs.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Charitablebusinessronin/Allura_Memory --skill code-review-charitablebusinessronin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Charitablebusinessronin/Allura_Memory/tree/main/.opencode/skills/code-review
Command: npx skills add https://github.com/Charitablebusinessronin/Allura_Memory --skill code-review-charitablebusinessronin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing code changes is time-consuming and error-prone. This skill provides a findings-first approach to identify correctness, regressions, security issues, contract drift, and missing tests while enforcing repository guardrails.

Core Features & Use Cases

  • Findings-first code review prioritizes concrete, actionable issues.
  • Repo-specific guardrails enforcement (append-only traces, promotion flow, server/client boundaries, and Zod validation).
  • Pre-merge risk assessment and audit trail for governance and accountability.
  • Use Case: PR reviews, branch diffs, and pre-merge assessments across software teams.

Quick Start

Review changed files and generate a findings-first report against repository guardrails.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code review for pull requests to catch security and correctness issues?

Automated code review applies a findings-first approach to pull requests and branch diffs, identifying correctness, regressions, security issues, and contract drift while enforcing repository guardrails before merge.

How are repository guardrails enforced during pre-merge risk assessment?

Pre-merge risk assessment enforces repo-specific invariants like append-only traces, SUPERSEDES relationships, and server/client boundaries, requiring verification tests and Zod validation to ensure data integrity.

What is findings-first code review and how does it prioritize issues?

Findings-first code review prioritizes concrete, actionable issues in code changes, focusing on correctness, security, data integrity, and guardrail compliance to generate a clear audit trail for governance and accountability.

Can I use this code review approach to detect contract drift and missing tests in branch diffs?

Yes, code review on branch diffs detects contract drift and missing verification tests by analyzing changes against repository invariants and enforcing proper validation through type checks and Zod schemas.

Does this code review method work without external dependencies or components?

Yes, this code review skill operates with zero external dependencies or components, analyzing software repository changes directly to provide a findings-first report against established guardrails.

What is the best way to audit code changes for HITL promotion flow and server/client boundaries?

Auditing code changes for promotion flow and server/client boundaries requires a findings-first review that enforces repository-specific invariants, including HITL for promotions and proper Zod validation checks.