WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Discover and apply organization coding standards from .forge-review/ configuration
Install Code Review Standards
$ npx skills add initializ/forge --skill code-review-standards -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install initializ/forge code-review-standards --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/initializ/forge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/forge-skills/local/embedded/code-review-standards .claude/skills/code-review-standards && 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-standards" agent skill from https://github.com/initializ/forge/tree/main/forge-skills/local/embedded/code-review-standards into .claude/skills/code-review-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review-standards", 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/initializ/forge/tree/main/forge-skills/local/embedded/code-review-standardsType 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 initializ/forge --skill code-review-standards -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install initializ/forge code-review-standards --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/initializ/forge.git skills-src && mkdir -p .agents/skills && cp -r skills-src/forge-skills/local/embedded/code-review-standards .agents/skills/code-review-standards && 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-standards" agent skill from https://github.com/initializ/forge/tree/main/forge-skills/local/embedded/code-review-standards into .agents/skills/code-review-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review-standards", 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 initializ/forge --skill code-review-standards -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install initializ/forge code-review-standards --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/initializ/forge.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/forge-skills/local/embedded/code-review-standards .cursor/skills/code-review-standards && 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-standards" agent skill from https://github.com/initializ/forge/tree/main/forge-skills/local/embedded/code-review-standards into .cursor/skills/code-review-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review-standards", 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/initializ/forge.git --path forge-skills/local/embedded/code-review-standards--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 initializ/forge --skill code-review-standards -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install initializ/forge code-review-standards --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/initializ/forge.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/forge-skills/local/embedded/code-review-standards .gemini/skills/code-review-standards && 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-standards" agent skill from https://github.com/initializ/forge/tree/main/forge-skills/local/embedded/code-review-standards into .gemini/skills/code-review-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review-standards", 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 initializ/forge code-review-standardsInstalls 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 initializ/forge --skill code-review-standards -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/initializ/forge.git skills-src && mkdir -p .github/skills && cp -r skills-src/forge-skills/local/embedded/code-review-standards .github/skills/code-review-standards && 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-standards" agent skill from https://github.com/initializ/forge/tree/main/forge-skills/local/embedded/code-review-standards into .github/skills/code-review-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review-standards", 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 initializ/forge --skill code-review-standards -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install initializ/forge code-review-standards --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/initializ/forge.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/forge-skills/local/embedded/code-review-standards .opencode/skills/code-review-standards && 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-standards" agent skill from https://github.com/initializ/forge/tree/main/forge-skills/local/embedded/code-review-standards into .opencode/skills/code-review-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review-standards", 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-standards- GitHub stars
- 222
- Token cost
- ~1.5k tokens
- SKILL.md length
- 431 words
- Files
- 9
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Discover and apply organization coding standards from .forge-review/ configuration
- Tasks that involve Code quality
- SKILL.md covers Overview, Directory Structure, Tool: review_standards_init and Tool: review_standards_check, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Code review
What it does
Code Review Standards is an agent skill from initializ/forge. Discover and apply organization coding standards from .forge-review/ configuration
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files (for example `templates/.forge-review/config.yaml`, `templates/.forge-review/standards/general.md` and `templates/.forge-review/standards/go.md`).
It sits in Development, covering Code quality and Code review. The repository describes itself as: Forge is the open-source runtime for Anthropic's Agent Skills standard — built for the agent that runs next to a service, in your environment, on infrastructure you already… The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Code quality
- Tasks that involve Code review
Example prompts
- “/code-review-standards”
What it can do on your machine
Read from SKILL.md and the folder at commit 3c608d8. 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 (its code samples are yaml and markdown).
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
Code Review Standards loads about 1.5k tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 431 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 initializ/forge at commit 3c608d8, republished under its Apache-2.0 licence (© initializ). 431 words, ~1,524 tokens.
Download SKILL.mdSave it as
.claude/skills/code-review-standards/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- code-review-standards
- description
- Discover and apply organization coding standards from .forge-review/ configuration
- icon
- 📏
- category
- developer
- tags
- code-review, standards, configuration, linting, quality
Code Review Standards
Teaches the agent to discover and apply organization-specific coding standards stored in a .forge-review/ directory in the target repository. This skill provides configuration templates and standard rule files that teams can customize.
Overview
The .forge-review/ directory is a convention for storing code review configuration alongside the codebase. When present, the code-review skill automatically loads these standards and applies them during reviews.
This skill:
- Documents the
.forge-review/directory structure and file formats - Provides templates for bootstrapping review standards in new repositories
- Teaches the agent how to discover and interpret standards files
Directory Structure
.forge-review/
├── config.yaml # Review configuration
├── .forge-review-ignore # Files/patterns to skip during review
└── standards/ # Coding standards (one file per topic)
├── general.md # General coding rules
├── security.md # Security rules
├── go.md # Go-specific rules
├── python.md # Python-specific rules
├── typescript.md # TypeScript rules
└── testing.md # Testing rulesTool: review_standards_init
Initialize a .forge-review/ directory in the current repository with default templates.
This is a binary-backed tool that uses filesystem operations (mkdir, write) to scaffold the standards directory. The agent reads templates bundled with this skill and writes them to the target repository.
Input:
| Parameter | Type | Required | Description |
|---|---|---|---|
| target_dir | string | no | Target directory (default: current working directory) |
| languages | array | no | Language-specific standards to include: go, python, typescript. Default: all |
| overwrite | boolean | no | Overwrite existing files. Default: false |
Output: List of created files and a summary of the initialized configuration.
Detection Heuristics
The agent selects this tool when it detects:
- Requests to "set up code review", "initialize review standards", "configure review"
- Questions about
.forge-review/directory structure - Requests to create or customize coding standards
Tool: review_standards_check
Check whether the current repository has a .forge-review/ configuration and report its status.
Input:
| Parameter | Type | Required | Description |
|---|---|---|---|
| target_dir | string | no | Directory to check (default: current working directory) |
Output: JSON object with configuration status, found files, and any validation issues.
Show full SKILL.md (171 more words)Show less
Detection Heuristics
The agent selects this tool when it detects:
- Questions about whether review standards are configured
- Requests to validate review configuration
- Troubleshooting review behavior
Configuration Reference
config.yaml
# .forge-review/config.yaml
version: "1"
# Default review settings
review:
# Focus areas to always include (bugs, security, style, performance, maintainability)
default_focus:
- bugs
- security
# Severity threshold: only report findings at or above this level
# Options: nitpick, info, warning, error
min_severity: info
# Maximum findings to report per review
max_findings: 50
# Language-specific settings
languages:
go:
standards_file: standards/go.md
enabled: true
python:
standards_file: standards/python.md
enabled: true
typescript:
standards_file: standards/typescript.md
enabled: true
# File patterns to always skip (supplements .forge-review-ignore)
skip_patterns:
- "vendor/**"
- "node_modules/**"
- "*.generated.go"
- "*.min.js"
- "**/*.pb.go".forge-review-ignore
Gitignore-style patterns for files that should be skipped during review:
# Dependencies
vendor/
node_modules/
# Generated code
*.generated.go
*.pb.go
*_gen.go
# Build artifacts
dist/
build/
*.min.js
*.min.css
# Test fixtures
testdata/
**/fixtures/**
# Documentation
*.md
LICENSEStandards Files
Standards files are markdown documents with rules organized by category. Each rule should be clear and actionable. The code-review skill injects these into the LLM prompt during review.
Format:
# Category Name
## Rule Title
Description of the rule and why it matters.
**Good:**
\`\`\`go
// example of correct code
\`\`\`
**Bad:**
\`\`\`go
// example of incorrect code
\`\`\`Templates
This skill bundles template files in the templates/ directory. Use review_standards_init to copy them into a target repository, or browse them directly for reference.
Available templates:
templates/.forge-review/config.yaml— Default configurationtemplates/.forge-review/.forge-review-ignore— Default ignore patternstemplates/.forge-review/standards/general.md— General coding standardstemplates/.forge-review/standards/security.md— Security review rulestemplates/.forge-review/standards/go.md— Go-specific standardstemplates/.forge-review/standards/python.md— Python-specific standardstemplates/.forge-review/standards/typescript.md— TypeScript standardstemplates/.forge-review/standards/testing.md— Testing standards
Safety Constraints
- This skill only reads and writes configuration files in
.forge-review/ - It never modifies source code
- Standards files are only used as additional context for LLM-based review; they do not block merges or fail CI on their own
- Overwrite protection is on by default (
overwrite: false)
© initializ, 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 8 other files in forge-skills/local/embedded/code-review-standards of initializ/forge.
- SKILL.md
- templates/.forge-review/.forge-review-ignore
- templates/.forge-review/config.yaml
- templates/.forge-review/standards/general.md
- templates/.forge-review/standards/go.md
- templates/.forge-review/standards/python.md
- templates/.forge-review/standards/security.md
- templates/.forge-review/standards/testing.md
- templates/.forge-review/standards/typescript.md
Open the folder on GitHubat commit 3c608d8
Compare with similar skills
Code Review Standards 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 Standards this skillinitializ/forge | 222 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence | |
| Skill Doli Code ReviewDolibarr/dolibarr | 7.7k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Dignified Python Standardsdocling-project/docling | 69k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Clean Code GuardamElnagdy/guard-skills | 1.3k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Archify Reviewtt-a1i/archify | 79k | — | ~415 | Automated safety check: Pass | MIT |
Similar skills
Skill Doli Code Review
Dolibarr/dolibarr
Reviews Dolibarr PHP code for compliance with coding standards and security best practices, and fixes identified issues.
Dignified Python Standards
docling-project/docling
Applies opinionated production Python conventions chosen by the project's Python version: modern type syntax, pathlib, explicit checks and interface guidance.
Clean Code Guard
amElnagdy/guard-skills
Reviews generated or changed production code against Clean Code, SOLID, DRY, KISS, YAGNI and LLM-specific failure modes before it ships, in any language.
Archify Review
tt-a1i/archify
Review Archify issues, PRs, or code through value, cost, and impact to support evidence-based maintenance decisions. Use for issue triage, change reviews, and…
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…
More from initializ/forge
All 15 skills in this repoCode Plan
initializ/forge
Turn a task description and repository into a structured implementation plan (files to create, files to modify, tests to add, risks).
Code Review
initializ/forge
AI-powered code review for diffs and individual files using LLM analysis
Codegen HTML
initializ/forge
Scaffold and iterate on standalone Preact + HTM applications with zero build dependencies
Code Agent
initializ/forge
General-purpose coding agent that reads, writes, and edits code, and searches codebases.
Codegen React
initializ/forge
Scaffold and iterate on Vite + React applications. An agent skill from initializ/forge.
K8s Cost Visibility
initializ/forge
Estimate Kubernetes infrastructure costs by querying cluster node, pod, PVC/PV, and LoadBalancer data, applying cloud pricing models, and producing cost attribution reports with storage and…
Related
Categories
Questions about Code Review Standards
What does Code Review Standards do?
Discover and apply organization coding standards from .forge-review/ configuration. Code Review Standards is an agent skill from initializ/forge.
When should I use Code Review Standards?
Code Review Standards fits situations like: tasks that involve Code quality; tasks that involve Code review.
How do I install Code Review Standards in Claude Code?
Run `npx skills add initializ/forge --skill code-review-standards -a claude-code`. Or copy the skill folder (forge-skills/local/embedded/code-review-standards in initializ/forge) into .claude/skills/code-review-standards in your project. Claude Code loads it when a task matches its description.
How do I install Code Review Standards in Codex?
Run `npx skills add initializ/forge --skill code-review-standards -a codex`. Or copy the skill folder (forge-skills/local/embedded/code-review-standards in initializ/forge) into .agents/skills/code-review-standards in your project. Codex loads it when a task matches its description.
Can I use Code Review Standards 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 initializ/forge --skill code-review-standards -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-standards, .gemini/skills/code-review-standards, .github/skills/code-review-standards and .opencode/skills/code-review-standards in your project.
What does Code Review Standards need to run?
SKILL.md names no scripts, command-line tools or credentials: Code Review Standards is instructions for the agent only.
Does Code Review Standards 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 Code Review Standards 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 Standards use?
Code Review Standards 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 Code Review Standards use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 Standards?
Skills that share tags, products or a category with Code Review Standards: WooCommerce Code Review (woocommerce/woocommerce, 11k stars), Skill Doli Code Review (Dolibarr/dolibarr, 7.7k stars), Dignified Python Standards (docling-project/docling, 69k stars) and Clean Code Guard (amElnagdy/guard-skills, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Code Review Standards?
initializ (a GitHub organization) maintains it in initializ/forge, which has 222 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 1, 2026.
Source: initializ/forge on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.