code-review

Automate code-review processes for staged or pushed changes using a deterministic context script and structured criteria.

450|36|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/kasperjunge/agent-resources --skill code-review-kasperjunge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/kasperjunge/agent-resources/tree/main/.opencode/skill/code-review
Command: npx skills add https://github.com/kasperjunge/agent-resources --skill code-review-kasperjunge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Streamlines and enforces rigorous evaluation of code changes to improve quality, maintainability, and architecture before they are committed or merged.

Core Features & Use Cases

  • Deterministic review context via a built-in script to gather changes, diffs, and branch context.
  • Structured review criteria covering code quality, debt, and architectural concerns.
  • Collaborative, adversarial-style review to surface issues and drive improvements.

Quick Start

Run scripts/collect_review_context.sh to begin the code-review workflow.

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?

Automated code review for pull requests is handled by a deterministic script that gathers diffs and branch context, applying a structured criteria framework to evaluate code quality and architecture before merging.

What is the best way to evaluate code quality and maintainability before a merge?

Evaluating code quality and maintainability requires a structured review criteria framework that assesses technical debt and architecture, using an adversarial-style review process to surface issues in staged changes.

Can I perform an architecture review on staged git changes?

Architecture review on staged git changes is supported by running the context collection script, which gathers the necessary diffs and branch context for a thorough evaluation of implementation and design.

How does the automated code review workflow handle technical debt?

The code review workflow handles technical debt by applying a structured criteria framework during the evaluation process, identifying maintainability issues and architectural concerns within the collected code diffs.

Do I need a specific environment to run the code review automation script?

Running the code review automation script requires a standard development environment with git access to collect branch context and diffs, requiring no additional dependencies to start the workflow.