Run any Skill in Manus with one click

Get Started

configure-reviews

Stars0

Forks1

UpdatedJune 9, 2026 at 11:39

Set up DeepWork Reviews — automated code review rules using .deepreview config files

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ncrmro

ncrmro/ks-config

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	configure-reviews
description	Set up DeepWork Reviews — automated code review rules using .deepreview config files

Configure DeepWork Reviews

Help the user set up automated code review rules for their project.

How to Use

Read the README_REVIEWS.md file in this plugin directory for the complete reference on DeepWork Reviews
Look at existing .deepreview files in the project that might have something related to what the user wants to do. Reuse existing rules / instructions if possible, including refactoring inline instructions that need to be reused into their own files in the .deepwork/review directory
Ask any clarifications needed using AskUserQuestion. Skip if you are clear on the need.
Create or update .deepreview YAML config files in the appropriate locations in their project
Test your change. Make a small change that should trigger the affected rule, then call mcp__deepwork__get_review_instructions and verify that the output includes text referencing your new rule. Be sure to revert the change.
Summarize your changes.
Ask the user if they'd like you to run a review now using the /review skill to try out the new configuration.

Important

Always read README_REVIEWS.md first (if you have not in this conversation already) — it contains the full configuration reference, examples, and glob pattern guide
Help users think about WHERE to place .deepreview files (project root for broad rules, subdirectories for scoped rules)
Write practical review instructions that will produce actionable feedback
Minimize reviewer count. Each review rule spawns a separate sub-agent with material overhead (context setup, API round-trips, teardown). Combine rules into a single rule whenever the joint instructions would not overload the reviewer's context. For example, running ruff and mypy on Python files should be one python_lint rule — not two separate rules — because the combined instructions are short and the file set is identical. Only split into separate rules when the instructions are long enough or distinct enough that merging them would degrade review quality.

More from this repository

same repository

deepplan

ncrmro/ks-config

Start structured planning — explores, designs, and produces an executable plan

2026-06-090

deepreviews

ncrmro/ks-config

Reference documentation for DeepWork Reviews — automated code review rules using .deepreview configs and DeepSchema-generated rules

2026-06-090

deepschema

ncrmro/ks-config

Create and manage DeepSchemas — rich file-level schemas with automatic validation and review generation

2026-06-090

deepwork

ncrmro/ks-config

Start or continue DeepWork workflows using MCP tools

2026-06-090

ks-agents

ncrmro/ks-config

Agent profile/skill maintenance — quickly edit ks-config/agents and commit + push successful changes

2026-06-090

ks-assistant

ncrmro/ks-config

Personal assistant — may start personal_assistant/reservation, personal_assistant/birthday, personal_assistant/calendar_prioritize, or personal_assistant/memory_search

2026-06-090

Configure DeepWork Reviews

Help the user set up automated code review rules for their project.

How to Use

Read the README_REVIEWS.md file in this plugin directory for the complete reference on DeepWork Reviews

Look at existing .deepreview files in the project that might have something related to what the user wants to do. Reuse existing rules / instructions if possible, including refactoring inline instructions that need to be reused into their own files in the .deepwork/review directory

Ask any clarifications needed using AskUserQuestion. Skip if you are clear on the need.

Create or update .deepreview YAML config files in the appropriate locations in their project

Test your change. Make a small change that should trigger the affected rule, then call mcp__deepwork__get_review_instructions and verify that the output includes text referencing your new rule. Be sure to revert the change.

Summarize your changes.

Ask the user if they'd like you to run a review now using the /review skill to try out the new configuration.

Important

Always read README_REVIEWS.md first (if you have not in this conversation already) — it contains the full configuration reference, examples, and glob pattern guide

Help users think about WHERE to place .deepreview files (project root for broad rules, subdirectories for scoped rules)

Write practical review instructions that will produce actionable feedback

Minimize reviewer count. Each review rule spawns a separate sub-agent with material overhead (context setup, API round-trips, teardown). Combine rules into a single rule whenever the joint instructions would not overload the reviewer's context. For example, running ruff and mypy on Python files should be one python_lint rule — not two separate rules — because the combined instructions are short and the file set is identical. Only split into separate rules when the instructions are long enough or distinct enough that merging them would degrade review quality.