Code Review Skill
awesome-skills/code-review-skill
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C/.NET, Kotlin, Swift, Dart…
Gives an agent the architecture knowledge and controller, service and template patterns needed to write correct, idiomatic code in the OpenOlat learning management system.
Install OpenOlat Developer Assistant
$ npx skills add OpenOLAT/OpenOLAT --skill openolat-dev -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OpenOLAT/OpenOLAT openolat-dev --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/OpenOLAT/OpenOLAT.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/openolat-dev .claude/skills/openolat-dev && 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 "openolat-dev" agent skill from https://github.com/OpenOLAT/OpenOLAT/tree/master/.claude/skills/openolat-dev into .claude/skills/openolat-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openolat-dev", 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/OpenOLAT/OpenOLAT/tree/master/.claude/skills/openolat-devType 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 OpenOLAT/OpenOLAT --skill openolat-dev -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OpenOLAT/OpenOLAT openolat-dev --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenOLAT/OpenOLAT.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/openolat-dev .agents/skills/openolat-dev && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "openolat-dev" agent skill from https://github.com/OpenOLAT/OpenOLAT/tree/master/.claude/skills/openolat-dev into .agents/skills/openolat-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openolat-dev", 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 OpenOLAT/OpenOLAT --skill openolat-dev -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OpenOLAT/OpenOLAT openolat-dev --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenOLAT/OpenOLAT.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/openolat-dev .cursor/skills/openolat-dev && 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 "openolat-dev" agent skill from https://github.com/OpenOLAT/OpenOLAT/tree/master/.claude/skills/openolat-dev into .cursor/skills/openolat-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openolat-dev", 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/OpenOLAT/OpenOLAT.git --path .claude/skills/openolat-dev--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 OpenOLAT/OpenOLAT --skill openolat-dev -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OpenOLAT/OpenOLAT openolat-dev --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenOLAT/OpenOLAT.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/openolat-dev .gemini/skills/openolat-dev && 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 "openolat-dev" agent skill from https://github.com/OpenOLAT/OpenOLAT/tree/master/.claude/skills/openolat-dev into .gemini/skills/openolat-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openolat-dev", 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 OpenOLAT/OpenOLAT openolat-devInstalls 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 OpenOLAT/OpenOLAT --skill openolat-dev -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OpenOLAT/OpenOLAT.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/openolat-dev .github/skills/openolat-dev && 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 "openolat-dev" agent skill from https://github.com/OpenOLAT/OpenOLAT/tree/master/.claude/skills/openolat-dev into .github/skills/openolat-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openolat-dev", 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 OpenOLAT/OpenOLAT --skill openolat-dev -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OpenOLAT/OpenOLAT openolat-dev --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenOLAT/OpenOLAT.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/openolat-dev .opencode/skills/openolat-dev && 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 "openolat-dev" agent skill from https://github.com/OpenOLAT/OpenOLAT/tree/master/.claude/skills/openolat-dev into .opencode/skills/openolat-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openolat-dev", 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
openolat-dev- GitHub stars
- 446
- Token cost
- ~6.9k tokens
- SKILL.md length
- 1,936 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Gives an agent the architecture knowledge and controller, service and template patterns needed to write correct, idiomatic code in the OpenOlat learning management system.
- Works in 4 steps: Presentation — Controllers, Components,… → Modules — Feature modules (course,… → Services — Business logic (*Manager… → …
- Writing a new controller, service, form or template in OpenOlat
- SKILL.md covers Project Basics, Architecture Overview, Controller Patterns and Event System, plus 18 more sections
- Calls mvn; reaches frentix.com and openolat.org
What it does
OpenOlat is a server-centric web framework where all UI state lives on the server and the browser only receives HTML fragments over AJAX, with no client-side framework such as React or Vue. The architecture has four layers: presentation, made of controllers, components and Velocity templates; feature modules such as course and portfolio; services holding business logic as Spring-managed interfaces; and persistence through Hibernate and JPA DAOs plus a database facade. A request flows from the servlet through a dispatcher and a synchronized window, finds a component by id, and fires an event to its controller, which runs logic against the database and services.
Controller patterns cover the hierarchy from the base Controller interface down through intermediate classes, noting that a form layout container is a layout container for form items rather than a controller, and that controllers are autowired so dependency-injected fields work directly in them. Example shapes are given for a basic controller and a form-based controller. The skill points to a condensed architecture file and a fuller document with numbered sections, marking patterns new to the current release line that do not exist on the previous branch. The project builds with Maven on Java 17 or later, using Jakarta EE, Spring 7 and Hibernate 7.
When your agent uses it
- Writing a new controller, service, form or template in OpenOlat
- Fixing a bug in the OpenOlat codebase
- Understanding how a request flows through OpenOlat's server-centric architecture
- Checking whether a pattern is new to the current release line
Example prompts
- “Create a new controller for the course settings page.”
- “Explain how a request reaches a Controller in OpenOlat's architecture.”
- “Is this form-controller pattern available on the previous release branch?”
Requirements
- A checkout of the OpenOlat repository
- Maven and Java 17 or later
- Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash(mvn *)
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Presentation — Controllers, Components, Velocity templates
- Modules — Feature modules (course, question pool, portfolio, groups, etc.)
- Services — Business logic (*Manager interfaces, Spring beans)
- Persistence — Hibernate/JPA DAOs, DB facade, VFS
What it can do on your machine
Read from SKILL.md and the folder at commit 1fefa0e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepGlobBash(mvn *)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
mvn
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
frentix.comopenolat.orgapache.org
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
OpenOlat Developer Assistant loads about 6.9k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 1,936 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,936 words (~6,921 tokens).
“You are an expert OpenOlat developer. Use the architecture knowledge below and the reference files to help developers write correct, idiomatic OpenOlat code.”
- name
- openolat-dev
- allowed-tools
- Read, Grep, Glob, Bash(mvn *)
Files
Just SKILL.md in .claude/skills/openolat-dev of OpenOLAT/OpenOLAT.
Open the folder on GitHubat commit 1fefa0e
Compare with similar skills
OpenOlat Developer Assistant 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 |
|---|---|---|---|---|---|---|
| OpenOlat Developer Assistant this skillOpenOLAT/OpenOLAT | 446 | — | ~6.9k | Automated safety check: Pass | Custom licence | |
| Code Review Skillawesome-skills/code-review-skill | 2.1k | — | ~2.8k | Automated safety check: Notes | MIT | |
| Java Architecture Reviewdecebals/claude-code-java | 750 | 1 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Code Review Excellenceandrew-yangy/gru-ai | 155 | — | ~1.7k | Automated safety check: Notes | MIT | |
| 707 Technologies Hexagonal Architecturejabrena/plinth | 445 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Component Boundary IdentifierArabelaTso/Skills-4-SE | 253 | — | ~2.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Java Architecture Review
decebals/claude-code-java
Reviews a Java project's architecture at the macro level: package structure, module boundaries, dependency direction and layering.
Code Review Excellence
andrew-yangy/gru-ai
Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, Python, and C/C++.
707 Technologies Hexagonal Architecture
jabrena/plinth
A skill your agent uses when you need framework-agnostic Hexagonal architecture guidance for Java projects - ports and adapters boundaries, application core independence, driving and driven…
Component Boundary Identifier
ArabelaTso/Skills-4-SE
Identifies boundaries between modules or components in software systems through static code analysis and dependency detection.
- Official
Project Workflow Analysis Blueprint Generator
github/awesome-copilot
Comprehensive technology-agnostic prompt generator for documenting end-to-end application workflows.
More from OpenOLAT/OpenOLAT
OpenOlat Frontend and Theming Guide
OpenOLAT/OpenOLAT
Covers OpenOlat's SASS theme architecture, CSS class conventions, DOM structure, and roughly 540 Java component renderers for styling work.
Related
Works with
Categories
Questions about OpenOlat Developer Assistant
What does OpenOlat Developer Assistant do?
Gives an agent the architecture knowledge and controller, service and template patterns needed to write correct, idiomatic code in the OpenOlat learning management system. OpenOlat is a server-centric web framework where all UI state lives on the server and the browser only receives HTML fragments over AJAX, with no client-side framework such as React or Vue. The architecture has four layers: presentation, made of controllers, components and Velocity templates; feature modules such as course and portfolio; services holding business logic as Spring-managed interfaces; and persistence through Hibernate and JPA DAOs plus a database facade.
When should I use OpenOlat Developer Assistant?
OpenOlat Developer Assistant fits situations like: writing a new controller, service, form or template in OpenOlat; fixing a bug in the OpenOlat codebase; understanding how a request flows through OpenOlat's server-centric architecture; checking whether a pattern is new to the current release line.
How do I install OpenOlat Developer Assistant in Claude Code?
Run `npx skills add OpenOLAT/OpenOLAT --skill openolat-dev -a claude-code`. Or copy the skill folder (.claude/skills/openolat-dev in OpenOLAT/OpenOLAT) into .claude/skills/openolat-dev in your project. Claude Code loads it when a task matches its description.
How do I install OpenOlat Developer Assistant in Codex?
Run `npx skills add OpenOLAT/OpenOLAT --skill openolat-dev -a codex`. Or copy the skill folder (.claude/skills/openolat-dev in OpenOLAT/OpenOLAT) into .agents/skills/openolat-dev in your project. Codex loads it when a task matches its description.
Can I use OpenOlat Developer Assistant 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 OpenOLAT/OpenOLAT --skill openolat-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openolat-dev, .gemini/skills/openolat-dev, .github/skills/openolat-dev and .opencode/skills/openolat-dev in your project.
What does OpenOlat Developer Assistant need to run?
Going by SKILL.md and its folder, OpenOlat Developer Assistant needs the command-line tools its instructions call (mvn). Our summary lists: A checkout of the OpenOlat repository; Maven and Java 17 or later. Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash(mvn *).
Does OpenOlat Developer Assistant access the network?
SKILL.md names 3 domains. In commands or code: frentix.com, openolat.org and apache.org; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is OpenOlat Developer Assistant 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 OpenOlat Developer Assistant use?
OpenOlat Developer Assistant has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does OpenOlat Developer Assistant use?
About 6.9k tokens (SKILL.md is roughly 28k 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 OpenOlat Developer Assistant?
Skills that share tags, products or a category with OpenOlat Developer Assistant: Code Review Skill (awesome-skills/code-review-skill, 2.1k stars), Java Architecture Review (decebals/claude-code-java, 750 stars), Code Review Excellence (andrew-yangy/gru-ai, 155 stars) and 707 Technologies Hexagonal Architecture (jabrena/plinth, 445 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains OpenOlat Developer Assistant?
OpenOLAT (a GitHub organization) maintains it in OpenOLAT/OpenOLAT, which has 446 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 6, 2026.
Source: OpenOLAT/OpenOLAT on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.