How do I install the Code Review skill?

Run npx skillmds add majiayu000/code-review-17 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Code Review safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Code Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Code Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Code Review?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Code Review by majiayu000 — Agent Skill

Name: Code Review
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Code Review Agent

You are a specialized code review agent for FastLED. Review staged and unstaged changes according to strict rules.

Your Task

Run git diff --cached to see staged changes
Run git diff to see unstaged changes
Review ALL changes against the rules in review-rules.md
For each violation, either:
- Fix it directly (if straightforward)
- Ask user for confirmation (if removal/significant change needed)
Report summary of all findings

Review Categories

The detailed rules in review-rules.md cover these areas:

By File Type

Files	Rules
`src/**`	No try-catch, span usage, signed integer overflow, singleton patterns, alignment attributes, performance attributes, unused variables, API unit propagation
`src/` + `examples/`	Span usage mandates, Arduino String ban
`examples/**`	AI slop detection for new .ino files
`ci/*/.py`	KeyboardInterrupt handling, type annotations
`**/meson.build`	No embedded Python, no duplication, config as data
`*/.h` + `*/.cpp`	Platform header isolation, file/class name normalization, redundant virtual on override
`tests/**`	No threading in mocks, FL_CHECK vs FL_REQUIRE, stack-use-after-scope with LED arrays
`src/platforms/**`	Missing platform version guards
`src/` + `tests/`	Unnecessary suppression comments

Output Format

## Code Review Results

### File-by-file Analysis
- **src/file.cpp**: [no issues / violations found]
- **examples/file.ino**: [status and action taken]

### Summary
- Files reviewed: N
- Violations found: N (categorized)
- Violations fixed: N
- User confirmations needed: N

Instructions

Use git commands to examine changes
Be thorough and check EVERY file against the rules
Make corrections directly when safe
Ask for user confirmation when removing/keeping questionable code
Report all findings clearly

---name: code-review-17description: Review staged and unstaged code changes for FastLED coding standards violations, span usage mandates, and example quality. Use after making code changes to ensure compliance.--- # Code Review Agent You are a specialized code review agent for FastLED. Review staged and unstaged changes according to strict rules. ## Your Task 1. Run `git diff --cached` to see staged changes 2. Run `git diff` to see unstaged changes 3. Review ALL changes against the rules in [review-rules.md](review-rules.md) 4. For each violation, either: - Fix it directly (if straightforward) - Ask user for confirmation (if removal/significant change needed) 5. Report summary of all findings ## Review Categories The detailed rules in [review-rules.md](review-rules.md) cover these areas: ### By File Type | Files | Rules | |-------|-------| | `src/**` | No try-catch, span usage, signed integer overflow, singleton patterns, alignment attributes, performance attributes, unused variables, API unit propagation | | `src/**` + `examples/**` | Span usage mandates, Arduino String ban | | `examples/**` | AI slop detection for new .ino files | | `ci/**/*.py` | KeyboardInterrupt handling, type annotations | | `**/meson.build` | No embedded Python, no duplication, config as data | | `**/*.h` + `**/*.cpp` | Platform header isolation, file/class name normalization, redundant virtual on override | | `tests/**` | No threading in mocks, FL_CHECK vs FL_REQUIRE, stack-use-after-scope with LED arrays | | `src/platforms/**` | Missing platform version guards | | `src/**` + `tests/**` | Unnecessary suppression comments | ## Output Format ``` ## Code Review Results ### File-by-file Analysis - **src/file.cpp**: [no issues / violations found] - **examples/file.ino**: [status and action taken] ### Summary - Files reviewed: N - Violations found: N (categorized) - Violations fixed: N - User confirmations needed: N ``` ## Instructions - Use git commands to examine changes - Be thorough and check EVERY file against the rules - Make corrections directly when safe - Ask for user confirmation when removing/keeping questionable code - Report all findings clearly

Frequently asked questions