skills.rest
diegocanepa
diegocanepaCOMMUNITY
Explore all skills by this author →
GitHub

swe-reviewer

Review code changes for a subtask and create a merge request.

Updated Feb 18, 2026
Search Tags:#automation#testing#quality assurance#code review#merge request#swe
One-click install
npx skills add https://github.com/diegocanepa/agent-skills --skill swe-reviewer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: swe-reviewer
Source: https://github.com/diegocanepa/agent-skills/tree/main/skills/swe-reviewer
Command: npx skills add https://github.com/diegocanepa/agent-skills --skill swe-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires vcs-branch, vcs-change-request, vcs-issue-management, backend-coder, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the rigorous review of code changes for individual subtasks, ensuring adherence to quality standards and architectural consistency before a merge request is created.

Core Features & Use Cases

  • Automated Quality Checks: Validates code against architectural guidelines, coding standards, testing coverage, and build success.
  • Focused Review: Ensures changes are strictly limited to the scope of the current subtask.
  • MR Generation: Creates a per-subtask Merge Request with a detailed description.
  • Issue Tracking: Updates project plans and posts progress to related issues.

Quick Start

Review the code changes for the current subtask and create a merge request if all quality checks pass.

Frequently Asked Questions about swe-reviewer

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

FAQPage Schema
How do I automate code review and merge request creation for individual subtasks?▼

Automated code review for subtasks validates architectural consistency, code quality, testing coverage, and build status. If all quality gates pass, it generates a per-subtask merge request with a detailed description automatically.

What does a comprehensive code review check before creating a merge request?▼

A comprehensive code review checks architectural consistency, coding standards, testing coverage, and build success. It ensures changes are strictly limited to the scope of the current subtask before proceeding to merge request generation.

Can I automatically update project plans and post progress to issues during code review?▼

Yes, automated code review updates project plans and posts progress updates to associated issues. This happens as part of the subtask review workflow after validating code quality and generating the merge request.

What dependencies are required to perform automated code review for merge requests?▼

Automated code review requires version control skills including vcs-branch, vcs-change-request, vcs-issue-management, and backend-coder. These dependencies enable branch management, issue tracking, and code generation operations.

How does automated code review enforce subtask scope and quality gates?▼

Automated code review enforces subtask scope by validating that changes are strictly limited to the current subtask. It requires adherence to specific quality gates covering architecture, code standards, testing coverage, and build status before merging.

Related Skills

Explore More Software Engineering Skills→
nrminornrminor

vcs-detect

Detect whether a project uses jj or git for version control.

Community
Basic
cloudvoyantcloudvoyant

pr-fix

Fetch open pull requests and generate proposed code fixes for unresolved review comments.

Official
Intermediate
cyanluna-gitcyanluna-git
173

review-backend

Analyze backend PRs across ten review perspectives and generate Korean PR comments.

Community
Advanced
pedronauckpedronauck
567

web-design-guidelines

Review UI code against Web Interface Guidelines for accessibility and design compliance.

Community
Intermediate