Code Reviewer
jewbetcha/opentrace
Comprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go.
OUDS Web compliance code review. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.
Install Code Review
$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill code-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap code-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/code-review .claude/skills/code-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "code-review" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/code-review into .claude/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/code-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill code-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap code-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/code-review .agents/skills/code-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "code-review" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/code-review into .agents/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill code-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap code-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/code-review .cursor/skills/code-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "code-review" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/code-review into .cursor/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git --path .github/skills/code-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill code-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap code-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/code-review .gemini/skills/code-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "code-review" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/code-review into .gemini/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap code-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill code-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/code-review .github/skills/code-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "code-review" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/code-review into .github/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill code-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap code-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/code-review .opencode/skills/code-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "code-review" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/code-review into .opencode/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
code-review- GitHub stars
- 222
- Token cost
- ~846 tokens
- SKILL.md length
- 275 words
- Files
- 1
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- MIT
At a glance
OUDS Web compliance code review. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.
- Works in 4 steps: Run git diff --stat to see changed files → For each file category, apply the… → Report violations with file, line, and… → …
- Reviewing a diff
- SKILL.md covers Purpose, Checklist, How to use and Report format
- Calls git
What it does
Code Review is an agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap. OUDS Web compliance code review. Use this skill when reviewing a diff, preparing a commit, or when asked to check code quality. Acts as a safety net that verifies all OUDS conventions are respected: token usage (no hardcoded values, no raw tokens), required mixins (border-radius, transition), accessibility (ARIA, focus-visible), multi-brand sync (tokens in all 3 brands), and file hygiene (no dist/, no auto-gen edits). Invoke proactively before any commit or PR submission.
Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Accessibility, Code review and CSS and styling. It works with JavaScript. The repository describes itself as: OUDS Web is an accessible, ergonomic and Orange branded framework based on Orange Unified Design System and Bootstrap. The licence is MIT.
When your agent uses it
- Reviewing a diff
- Preparing a commit
- Asked to check code quality
Example prompts
- “/code-review”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Run git diff --stat to see changed files
- For each file category, apply the relevant checklist section
- Report violations with file, line, and suggested fix
- Classify: ERROR (must fix) vs WARNING (should fix)
What it can do on your machine
Read from SKILL.md and the folder at commit 27508ab. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Code Review loads about 846 tokens when it runs. Until then it costs about 122 tokens; SKILL.md has 275 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Orange-OpenSource/Orange-Boosted-Bootstrap at commit 27508ab, republished under its MIT licence (© Orange-OpenSource). 275 words, ~846 tokens.
Download SKILL.mdSave it as
.claude/skills/code-review/SKILL.md (or your agent's skills folder).- name
- code-review
- description
- OUDS Web compliance code review. Use this skill when reviewing a diff, preparing a commit, or when asked to check code quality. Acts as a safety net that verifies all OUDS conventions are respected: token usage (no hardcoded values, no raw tokens), required mixins (border-radius, transition), accessibility (ARIA, focus-visible), multi-brand sync (tokens in all 3 brands), and file hygiene (no dist/, no auto-gen edits). Invoke proactively before any commit or PR submission.
Code Review (OUDS Compliance)
Purpose
This skill is a safety net. It catches OUDS convention violations that other skills might have missed. Invoke it before committing or when reviewing diffs.
Checklist
For each changed file in the diff, verify:
SCSS files (**/*.scss)
- No hardcoded values — colors (
#xxx), spacing (16px), dimensions must use tokens - No raw tokens —
$core-ouds-*,$core-orange-*,$core-sosh-*never in component SCSS - Mixins used —
@include border-radius()and@include transition()(never direct properties) -
border: 0— notborder: none - No
lighten()/darken()— use token variant -
!defaulton variables — every module-scope SCSS variable - Colors via CSS custom props —
var(--#{$prefix}color-*)for dark mode -
color-mode()mixin — not raw[data-bs-theme]orprefers-color-scheme -
#{$ouds-root-selector}— not:rootdirectly -
// OUDS mod:comment on Bootstrap deviations
JavaScript files (js/src/**/*.js)
- No semicolons
- No trailing commas
- Template literals (not concatenation)
-
.jsextension on imports - No
console.*injs/src/ -
'use strict'at top - Extends
BaseComponent(if it's a component)
HTML/MDX files
- Semantic elements —
<button>for actions,<a>for links - ARIA attributes — correct for the interaction pattern
-
.visually-hidden— notdisplay: nonefor SR content -
data-bs-theme— notprefers-color-schemefor color modes
Token/brand files (packages/**)
- Auto-generated files not modified —
_raw.scss,_semantic.scss,_component.scss,_*-custom-props.scss - New tokens in all 3 brands — if a new
$ouds-<comp>-*was added - Import order preserved — in
_index.scss
General
- No
dist/files in the diff - No JS in
packages/<brand>/— JS is shared - Focus visible —
@include focus-visible()on interactive elements - Touch targets — 44×44px minimum on new interactive elements
How to use
- Run
git diff --statto see changed files - For each file category, apply the relevant checklist section
- Report violations with file, line, and suggested fix
- Classify: ERROR (must fix) vs WARNING (should fix)
Report format
## Code Review: OUDS Compliance
### ❌ Errors (must fix before merge)
- `scss/_buttons.scss:42` — hardcoded `padding: 8px` → use `$ouds-space-*` token
- `js/src/tooltip.js:15` — semicolon present → remove
### ⚠️ Warnings (should fix)
- `scss/_card.scss:88` — missing `// OUDS mod:` on Bootstrap override
### ✅ Passed
- Token cross-brand check: all present
- No dist/ files in diff
- ARIA attributes correct© Orange-OpenSource, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/code-review of Orange-OpenSource/Orange-Boosted-Bootstrap.
Open the folder on GitHubat commit 27508ab
Compare with similar skills
Code Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Code Review this skillOrange-OpenSource/Orange-Boosted-Bootstrap | 222 | — | ~846 | Automated safety check: Pass | MIT | |
| Code Reviewerjewbetcha/opentrace | 116 | 2 repos | ~1.1k | Automated safety check: Notes | MIT | |
| Cross-Language Coding Standardszereight/gitlab-mcp | 2k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Codebase Review SwarmZaxbyHub/opencode-swarm | 490 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Code ReviewerLeoYeAI/openclaw-master-skills | 2.2k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Aidd Reviewparalleldrive/aidd | 384 | — | ~945 | Automated safety check: Pass | MIT |
Similar skills
Cross-Language Coding Standards
zereight/gitlab-mcp
Shared reference for naming, function size, complexity and error handling rules that reviewer agents apply across TypeScript, Python, Go, Rust, Java, C# and Swift.
Codebase Review Swarm
ZaxbyHub/opencode-swarm
Runs an evidence-gated, quote-grounded audit of a codebase for security, QA, accessibility, performance and more, and writes a verified report without changing source files.
Code Reviewer
LeoYeAI/openclaw-master-skills
Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin.
Aidd Review
paralleldrive/aidd
Conduct a thorough code review focusing on code quality, best practices, security, test coverage, and adherence to project standards and functional requirements.
Code Reviewer
borghei/Claude-Skills
Code review automation for TypeScript, JavaScript, Python, Go, Swift, and Kotlin.
More from Orange-OpenSource/Orange-Boosted-Bootstrap
All 13 skills in this repoToken System
Orange-OpenSource/Orange-Boosted-Bootstrap
OUDS design token system rules and architecture. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.
Using Ouds Web Version Major Minor
Orange-OpenSource/Orange-Boosted-Bootstrap
Provides comprehensive knowledge of the OUDS Web library (Orange Unified Design System for Web), a Bootstrap-based CSS/JS framework for building Orange-branded web interfaces.
Component Patterns
Orange-OpenSource/Orange-Boosted-Bootstrap
SCSS and JS structural patterns for OUDS Web components. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.
Create Component
Orange-OpenSource/Orange-Boosted-Bootstrap
Step-by-step workflow for creating a new SCSS and/or JavaScript component in OUDS Web.
Diagnose Errors
Orange-OpenSource/Orange-Boosted-Bootstrap
Diagnostic workflow for build, lint, CI, and test errors in OUDS Web.
Javascript Conventions
Orange-OpenSource/Orange-Boosted-Bootstrap
JavaScript coding conventions for OUDS Web. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.
Related
Works with
Categories
Questions about Code Review
What does Code Review do?
OUDS Web compliance code review. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap. Code Review is an agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap. OUDS Web compliance code review.
When should I use Code Review?
Code Review fits situations like: reviewing a diff; preparing a commit; asked to check code quality.
How do I install Code Review in Claude Code?
Run `npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill code-review -a claude-code`. Or copy the skill folder (.github/skills/code-review in Orange-OpenSource/Orange-Boosted-Bootstrap) into .claude/skills/code-review in your project. Claude Code loads it when a task matches its description.
How do I install Code Review in Codex?
Run `npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill code-review -a codex`. Or copy the skill folder (.github/skills/code-review in Orange-OpenSource/Orange-Boosted-Bootstrap) into .agents/skills/code-review in your project. Codex loads it when a task matches its description.
Can I use Code Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill code-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-review, .gemini/skills/code-review, .github/skills/code-review and .opencode/skills/code-review in your project.
What does Code Review need to run?
Going by SKILL.md and its folder, Code Review needs the command-line tools its instructions call (git).
Does Code Review access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Code Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Code Review use?
Code Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Code Review use?
About 846 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Code Review?
Skills that share tags, products or a category with Code Review: Code Reviewer (jewbetcha/opentrace, 116 stars), Cross-Language Coding Standards (zereight/gitlab-mcp, 2k stars), Codebase Review Swarm (ZaxbyHub/opencode-swarm, 490 stars) and Code Reviewer (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Code Review?
Orange-OpenSource (a GitHub organization) maintains it in Orange-OpenSource/Orange-Boosted-Bootstrap, which has 222 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.
Source: Orange-OpenSource/Orange-Boosted-Bootstrap on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.