Run any Skill in Manus with one click

code-review-guideline-skill

Stars0

Forks0

UpdatedMarch 18, 2026 at 13:18

describe how to review code with best practices, use when user ask for help with code review or you need to implement the code

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

ambersun1234

ambersun1234/skills

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	code review guideline skill
description	describe how to review code with best practices, use when user ask for help with code review or you need to implement the code

code review guidelines

the document outlines the best practices for what a good code looks like, a good codebase should follow these guidelines.

when to use this skill

when user ask to review code, ask help with the code review or when you need to implement the code

guidelines

don't write any comments that describe what the code does in the codebase, write comments only if the code is not obvious or if the user asks for it
write comments only to describe why the code is written a certain way, not what it does
avoid unclear variable names, use names that are clear and concise
avoid multi layer nested if statements or for loops, refactor them with functions or classes
use third party packages whenever possible, don't reinvent the wheel
always making sure abstraction layer is constructed between different layers of the codebase, don't put all the logic in the same layer
log the error and success messages in proper location whenever possible
make type alias whenever possible, simple int, string cannot easily tell the difference between them, use type alias to make it clear, for example, use UserId instead of int

More from this repository

same repository

cache-skill

ambersun1234/skills

describe how to write cache related code in the codebase, use when you need to add or modify cache related code or user ask to optimize the cache related code to the codebase

2026-02-090

database-skill

ambersun1234/skills

describe how to write database related code in the codebase, use when you need to add or modify database related code or user ask to optimize to the codebase

2026-02-090

integration-test-skill

ambersun1234/skills

describe how to write integration tests or general tests for the codebase, use when you need to add or modify integration tests to the codebase

2026-02-090

logging-best-practice-skill

ambersun1234/skills

describe how to do the logging in the codebase, use when you need to add logger to the codebase

2026-02-090

message-queue-skill

ambersun1234/skills

describe how to write message queue related code in the codebase, use when you need to add or modify message queue related code or user ask to optimize the message queue related code to the codebase

2026-02-090

middleware-skill

ambersun1234/skills

describe how to write middleware code in the codebase, use when you need a filter or interceptor to process the request or response

2026-02-090

name	code review guideline skill
description	describe how to review code with best practices, use when user ask for help with code review or you need to implement the code

code review guidelines

the document outlines the best practices for what a good code looks like, a good codebase should follow these guidelines.

when to use this skill

when user ask to review code, ask help with the code review or when you need to implement the code

guidelines

don't write any comments that describe what the code does in the codebase, write comments only if the code is not obvious or if the user asks for it
write comments only to describe why the code is written a certain way, not what it does
avoid unclear variable names, use names that are clear and concise
avoid multi layer nested if statements or for loops, refactor them with functions or classes
use third party packages whenever possible, don't reinvent the wheel
always making sure abstraction layer is constructed between different layers of the codebase, don't put all the logic in the same layer
log the error and success messages in proper location whenever possible
make type alias whenever possible, simple int, string cannot easily tell the difference between them, use type alias to make it clear, for example, use UserId instead of int