Archify Diagrams
tt-a1i/archify
Creates interactive architecture, workflow, sequence, data-flow and lifecycle diagrams as standalone HTML with inline SVG, themes and image or video export.
Review local code, diffs, modules, directories, or design changes for consequential architecture issues when the user explicitly asks for architecture review, when an upstream review routes…
Install Architecture Review
$ npx skills add HorizonRobotics/RoboOrchardLab --skill architecture-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install HorizonRobotics/RoboOrchardLab architecture-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/HorizonRobotics/RoboOrchardLab.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/codereview/architecture-review .claude/skills/architecture-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 "architecture-review" agent skill from https://github.com/HorizonRobotics/RoboOrchardLab/tree/master/.agents/skills/codereview/architecture-review into .claude/skills/architecture-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-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/HorizonRobotics/RoboOrchardLab/tree/master/.agents/skills/codereview/architecture-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 HorizonRobotics/RoboOrchardLab --skill architecture-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install HorizonRobotics/RoboOrchardLab architecture-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HorizonRobotics/RoboOrchardLab.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/codereview/architecture-review .agents/skills/architecture-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 "architecture-review" agent skill from https://github.com/HorizonRobotics/RoboOrchardLab/tree/master/.agents/skills/codereview/architecture-review into .agents/skills/architecture-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-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 HorizonRobotics/RoboOrchardLab --skill architecture-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install HorizonRobotics/RoboOrchardLab architecture-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HorizonRobotics/RoboOrchardLab.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/codereview/architecture-review .cursor/skills/architecture-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 "architecture-review" agent skill from https://github.com/HorizonRobotics/RoboOrchardLab/tree/master/.agents/skills/codereview/architecture-review into .cursor/skills/architecture-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-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/HorizonRobotics/RoboOrchardLab.git --path .agents/skills/codereview/architecture-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 HorizonRobotics/RoboOrchardLab --skill architecture-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install HorizonRobotics/RoboOrchardLab architecture-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HorizonRobotics/RoboOrchardLab.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/codereview/architecture-review .gemini/skills/architecture-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 "architecture-review" agent skill from https://github.com/HorizonRobotics/RoboOrchardLab/tree/master/.agents/skills/codereview/architecture-review into .gemini/skills/architecture-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-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 HorizonRobotics/RoboOrchardLab architecture-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 HorizonRobotics/RoboOrchardLab --skill architecture-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/HorizonRobotics/RoboOrchardLab.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/codereview/architecture-review .github/skills/architecture-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 "architecture-review" agent skill from https://github.com/HorizonRobotics/RoboOrchardLab/tree/master/.agents/skills/codereview/architecture-review into .github/skills/architecture-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-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 HorizonRobotics/RoboOrchardLab --skill architecture-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 HorizonRobotics/RoboOrchardLab architecture-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HorizonRobotics/RoboOrchardLab.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/codereview/architecture-review .opencode/skills/architecture-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 "architecture-review" agent skill from https://github.com/HorizonRobotics/RoboOrchardLab/tree/master/.agents/skills/codereview/architecture-review into .opencode/skills/architecture-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-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
architecture-review- GitHub stars
- 174
- Token cost
- ~1k tokens
- SKILL.md length
- 449 words
- Files
- 2
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Review local code, diffs, modules, directories, or design changes for consequential architecture issues when the user explicitly asks for architecture review, when an upstream review routes…
- Works in 7 steps: Determine the review target and scope. → Gather only the in-scope guidance locally. → Produce a concise structural summary… → …
- Explicitly asks for architecture review
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- An upstream review routes architecture-sensitive scope here
What it does
Architecture Review is an agent skill from HorizonRobotics/RoboOrchardLab. Review local code, diffs, modules, directories, or design changes for consequential architecture issues when the user explicitly asks for architecture review, when an upstream review routes architecture-sensitive scope here, or when the current review/evaluation request is primarily architectural.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `REPORT_TEMPLATE.md`).
It sits in Development, covering Software architecture. The licence is Apache-2.0.
When your agent uses it
- Explicitly asks for architecture review
- An upstream review routes architecture-sensitive scope here
- The current review/evaluation request is primarily architectural
Example prompts
- “/architecture-review”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Determine the review target and scope.
- Gather only the in-scope guidance locally.
- Produce a concise structural summary before finding issues.
- Launch one strong architecture-review subagent for the current round by
- Validate each candidate locally.
- Filter and de-duplicate.
- Output a report using REPORT_TEMPLATE.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 221ec0e. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Architecture Review loads about 1k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 449 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 HorizonRobotics/RoboOrchardLab at commit 221ec0e, republished under its Apache-2.0 licence (© HorizonRobotics). 449 words, ~1,000 tokens.
Download SKILL.mdSave it as
.claude/skills/architecture-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- architecture-review
- description
- Review local code, diffs, modules, directories, or design changes for consequential architecture issues when the user explicitly asks for architecture review, when an upstream review routes architecture-sensitive scope here, or when the current review/evaluation request is primarily architectural.
Provide an architecture review for the given local target.
Use this skill after .agents/skills/codereview/SKILL.md routes the task
here. Read ../references/triggering-and-signal.md and
../references/review-depth-and-delegation.md first.
Do not use this skill for ordinary PR/MR bug review when architecture is not
the main or clearly material question. Use ../prmr-codereview/SKILL.md for
that flow. Do not use this skill for routine implementation self-checks or
casual cleanup opinions.
Follow ../references/review-depth-and-delegation.md. The main agent owns
scope, structural summary, guidance discovery, and candidate validation. Each
architecture-review round defaults to one strong review subagent covering all
applicable architecture dimensions.
To do this:
Determine the review target and scope.
- Identify whether the target is a local directory, file set, git diff, branch diff, or design-oriented change.
- Identify the paths that actually belong to the requested scope.
- If the request is ambiguous, choose the smallest reasonable scope that satisfies it.
Gather only the in-scope guidance locally.
- Load this repository's root
AGENTS.mdfile, if it exists. - Load directory-scoped
AGENTS.mdfiles that apply to the target. - Load referenced
.agents/instructions/,.agents/references/, and.agents/skills/files that are relevant to the review. - Always include
.agents/references/architecture-review-guideline.mdwhen it is in scope. - Load applicable package-local supplements only after the repository root baseline.
- Load this repository's root
Produce a concise structural summary before finding issues.
- Summarize the main layers, contracts, and caller-facing boundaries.
- State which architecture dimensions are materially relevant.
- For abstraction-heavy targets, name the smallest viable one-method or no-new-class alternative before accepting new protocols, providers, adapters, factories, registries, DTOs, snapshots, or caches.
Launch one strong architecture-review subagent for the current round by default. Require one structured candidate list covering:
- boundaries, dependency direction, and ownership
- contracts, compatibility, and public surfaces
- abstraction minimality, readability, and evolvability
Keep only candidates with a concrete architectural problem, clear impact, and enough evidence to validate within the reviewed scope. The reviewer must check whether proposed abstractions remove real complexity or only add indirection, and name deletable surfaces when a simpler owner method, helper, or existing contract would carry the same behavior.
Validate each candidate locally.
- Confirm the problem and claimed impact against current call sites and ownership boundaries.
- For overdesign findings, validate the proposed smaller shape.
- Confirm that cited
AGENTS.md/.agentsrules are in scope. - Keep the current reviewer responsible for verifying fixes to its own findings. After its ledger is resolved, use a fresh reviewer for the next issue-discovery round. Do not launch separate validator agents by default.
Filter and de-duplicate.
- Remove unvalidated issues.
- Merge overlapping candidates.
- Keep only high-signal findings.
Output a report using
REPORT_TEMPLATE.md.- State the reviewed scope and architecture dimensions.
- Include minimality or overdesign in the reviewed dimensions when material.
- If no issues were found, use the exact text:
No issues found. Checked the reviewed architecture dimensions.
© HorizonRobotics, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/codereview/architecture-review of HorizonRobotics/RoboOrchardLab.
- SKILL.md
- REPORT_TEMPLATE.md
Open the folder on GitHubat commit 221ec0e
Compare with similar skills
Architecture 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 |
|---|---|---|---|---|---|---|
| Architecture Review this skillHorizonRobotics/RoboOrchardLab | 174 | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Archify Diagramstt-a1i/archify | 82k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Electron Multi-Process ArchitectureiOfficeAI/AionUi | 33k | 1 repos | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Backend Code Reviewlanggenius/dify | 158k | — | ~676 | Automated safety check: Pass | Custom licence | |
| Dark Architecture Diagram BuilderCocoon-AI/architecture-diagram-generator | 7.4k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| SVG Diagram GeneratorJimLiu/baoyu-skills | 27k | 1 repos | ~3.1k | Automated safety check: Pass | MIT |
Similar skills
Electron Multi-Process Architecture
iOfficeAI/AionUi
Tells the agent where new code belongs in an Electron multi-process project and which APIs each process may use, with rules for new bridges, services, agents and workers.
Backend Code Review
langgenius/dify
Reviews backend code under api/ for concrete, reproducible defects, routes to rule packs for architecture, schema, repositories and SQLAlchemy, and ranks findings from P0 to P3.
Dark Architecture Diagram Builder
Cocoon-AI/architecture-diagram-generator
Creates dark-themed system, cloud, security and network architecture diagrams as self-contained HTML files with inline SVG and CSS.
SVG Diagram Generator
JimLiu/baoyu-skills
Creates standalone dark-themed SVG diagrams, including architecture, flowchart, sequence, structural, mind map, timeline and state machine types.
Senior Architect Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin…
More from HorizonRobotics/RoboOrchardLab
All 8 skills in this repoFeature Dev
HorizonRobotics/RoboOrchardLab
Guided feature development with codebase understanding and architecture focus.
Codereview Family
HorizonRobotics/RoboOrchardLab
Structured code review family for explicit heavy review requests and architecture-sensitive review/evaluation requests.
Prmr Codereview
HorizonRobotics/RoboOrchardLab
Review a GitHub PR or GitLab MR when the task is a PR/MR review or comment flow.
Code Architect
HorizonRobotics/RoboOrchardLab
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create or modify, component…
Code Explorer
HorizonRobotics/RoboOrchardLab
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development.
Code Reviewer
HorizonRobotics/RoboOrchardLab
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that…
Related
Categories
Questions about Architecture Review
What does Architecture Review do?
Review local code, diffs, modules, directories, or design changes for consequential architecture issues when the user explicitly asks for architecture review, when an upstream review routes…. Architecture Review is an agent skill from HorizonRobotics/RoboOrchardLab. Review local code, diffs, modules, directories, or design changes for consequential architecture issues when the user explicitly asks for architecture review, when an upstream review routes architecture-sensitive scope here, or when the current review/evaluation request is primarily architectural.
When should I use Architecture Review?
Architecture Review fits situations like: explicitly asks for architecture review; an upstream review routes architecture-sensitive scope here; the current review/evaluation request is primarily architectural.
How do I install Architecture Review in Claude Code?
Run `npx skills add HorizonRobotics/RoboOrchardLab --skill architecture-review -a claude-code`. Or copy the skill folder (.agents/skills/codereview/architecture-review in HorizonRobotics/RoboOrchardLab) into .claude/skills/architecture-review in your project. Claude Code loads it when a task matches its description.
How do I install Architecture Review in Codex?
Run `npx skills add HorizonRobotics/RoboOrchardLab --skill architecture-review -a codex`. Or copy the skill folder (.agents/skills/codereview/architecture-review in HorizonRobotics/RoboOrchardLab) into .agents/skills/architecture-review in your project. Codex loads it when a task matches its description.
Can I use Architecture 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 HorizonRobotics/RoboOrchardLab --skill architecture-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/architecture-review, .gemini/skills/architecture-review, .github/skills/architecture-review and .opencode/skills/architecture-review in your project.
What does Architecture Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Architecture Review is instructions for the agent only.
Does Architecture Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Architecture 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 Architecture Review use?
Architecture Review is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Architecture Review use?
About 1k tokens (SKILL.md is roughly 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 Architecture Review?
Skills that share tags, products or a category with Architecture Review: Archify Diagrams (tt-a1i/archify, 82k stars), Electron Multi-Process Architecture (iOfficeAI/AionUi, 33k stars), Backend Code Review (langgenius/dify, 158k stars) and Dark Architecture Diagram Builder (Cocoon-AI/architecture-diagram-generator, 7.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Architecture Review?
HorizonRobotics (a GitHub organization) maintains it in HorizonRobotics/RoboOrchardLab, which has 174 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on September 24, 2026.
Source: HorizonRobotics/RoboOrchardLab on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.