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.
Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance.
Install Structured Code Review
$ npx skills add rohitg00/skillkit --skill structured-code-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rohitg00/skillkit structured-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/rohitg00/skillkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/core/src/methodology/packs/collaboration/structured-review .claude/skills/structured-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 "structured-code-review" agent skill from https://github.com/rohitg00/skillkit/tree/main/packages/core/src/methodology/packs/collaboration/structured-review into .claude/skills/structured-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structured-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/rohitg00/skillkit/tree/main/packages/core/src/methodology/packs/collaboration/structured-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 rohitg00/skillkit --skill structured-code-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rohitg00/skillkit structured-code-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rohitg00/skillkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/core/src/methodology/packs/collaboration/structured-review .agents/skills/structured-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 "structured-code-review" agent skill from https://github.com/rohitg00/skillkit/tree/main/packages/core/src/methodology/packs/collaboration/structured-review into .agents/skills/structured-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structured-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 rohitg00/skillkit --skill structured-code-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rohitg00/skillkit structured-code-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rohitg00/skillkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/core/src/methodology/packs/collaboration/structured-review .cursor/skills/structured-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 "structured-code-review" agent skill from https://github.com/rohitg00/skillkit/tree/main/packages/core/src/methodology/packs/collaboration/structured-review into .cursor/skills/structured-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structured-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/rohitg00/skillkit.git --path packages/core/src/methodology/packs/collaboration/structured-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 rohitg00/skillkit --skill structured-code-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rohitg00/skillkit structured-code-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rohitg00/skillkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/core/src/methodology/packs/collaboration/structured-review .gemini/skills/structured-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 "structured-code-review" agent skill from https://github.com/rohitg00/skillkit/tree/main/packages/core/src/methodology/packs/collaboration/structured-review into .gemini/skills/structured-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structured-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 rohitg00/skillkit structured-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 rohitg00/skillkit --skill structured-code-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rohitg00/skillkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/core/src/methodology/packs/collaboration/structured-review .github/skills/structured-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 "structured-code-review" agent skill from https://github.com/rohitg00/skillkit/tree/main/packages/core/src/methodology/packs/collaboration/structured-review into .github/skills/structured-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structured-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 rohitg00/skillkit --skill structured-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 rohitg00/skillkit structured-code-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rohitg00/skillkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/core/src/methodology/packs/collaboration/structured-review .opencode/skills/structured-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 "structured-code-review" agent skill from https://github.com/rohitg00/skillkit/tree/main/packages/core/src/methodology/packs/collaboration/structured-review into .opencode/skills/structured-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "structured-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
structured-code-review- GitHub stars
- 1.5k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 404 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance.
- Works in 5 steps: Requirements Compliance → Correctness → Code Quality → …
- The user asks for code review
- SKILL.md covers Core Principle, Review Stages, Writing Good Feedback and Review Checklist Summary, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Structured Code Review is an agent skill from rohitg00/skillkit. Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR feedback, pull request review, or wants their code checked for bugs, style issues, or vulnerabilities — triggered by phrases like "review my code", "check this PR", "review my changes", "pull request…
Its SKILL.md is about 1.3k 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 Pull requests, Code review and Code quality. The repository describes itself as: Supercharge AI coding agents with portable skills. Install, translate & share skills across Claude Code, Cursor, Codex, Copilot & 40 more. The licence is Apache-2.0.
When your agent uses it
- The user asks for code review
- Pull request review
- Wants their code checked for bugs
- Vulnerabilities — triggered by phrases like review my code
Example prompts
- “review my code”
- “check this PR”
- “review my changes”
- “/structured-code-review”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit d2e5c34. 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 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
Structured Code Review loads about 1.3k tokens when it runs. Until then it costs about 141 tokens; SKILL.md has 404 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 rohitg00/skillkit at commit d2e5c34, republished under its Apache-2.0 licence (© rohitg00). 404 words, ~1,257 tokens.
Download SKILL.mdSave it as
.claude/skills/structured-code-review/SKILL.md (or your agent's skills folder).- name
- structured-code-review
- description
- Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR feedback, pull request review, or wants their code checked for bugs, style issues, or vulnerabilities — triggered by phrases like "review my code", "check this PR", "review my changes", "pull request review", or "code feedback".
- version
- 1.0.0
- triggers
- code review, review this, feedback on code, PR review, review my changes
- tags
- collaboration, code-review, quality, feedback
- difficulty
- intermediate
- estimatedTime
- 15
- relatedSkills
- collaboration/parallel-investigation, planning/verification-gates
Structured Code Review
You are performing a structured, multi-stage code review. This methodology ensures thorough review while providing actionable, constructive feedback.
Core Principle
Review in stages. Each stage has a specific focus. Don't mix concerns.
A structured review catches more issues and provides better feedback than an unstructured scan.
Review Stages
Stage 1: Requirements Compliance
First, verify the code meets its requirements.
Checklist:
- Implements stated requirements
- Handles specified edge cases
- No scope creep (unexpected additions)
- No missing functionality
Feedback at this stage:
- "This doesn't appear to handle the case when X is empty"
- "The requirement specified Y, but this implements Z"
- "This adds feature F which wasn't requested - is that intentional?"
Stage 2: Correctness
Next, verify the code works correctly.
Checklist:
- Logic is sound
- No obvious bugs
- Error paths are handled
- No unfinished code (TODOs without tickets)
Feedback at this stage:
- "This will throw if
useris null" - "The loop exits early before processing all items"
- "What happens when the API call fails?"
Stage 3: Code Quality
Then, evaluate code quality and maintainability.
Checklist:
- Clear naming
- Reasonable function/method length
- No unnecessary complexity
- Follows project conventions
- Appropriate abstractions
Feedback at this stage:
- "Could you rename
datatouserProfilefor clarity?" - "This function is doing three things - consider splitting"
- "We use camelCase for variables in this project"
Show full SKILL.md (189 more words)Show less
Stage 4: Testing
Evaluate test coverage and quality.
Checklist:
- New code has tests
- Tests cover main paths and edge cases
- Tests are readable and maintainable
- Tests don't test implementation details
Feedback at this stage:
- "Please add a test for the error case"
- "This test will break if we change the implementation"
- "Consider using a parameterized test for these cases"
Stage 5: Security & Performance
Finally, check for security and performance concerns.
Checklist:
- No SQL injection, XSS, etc.
- Secrets not exposed
- No obvious N+1 queries
- No unnecessary computation
- Sensitive data handled correctly
Feedback at this stage:
- "This input should be sanitized before use"
- "Consider adding an index for this query"
- "This API key should come from environment variables"
Writing Good Feedback
Feedback Levels
| Level | When to Use | Example |
|---|---|---|
| Blocker | Must fix before merge | "Security: This allows SQL injection" |
| Major | Should fix, but not critical | "This will fail for empty arrays" |
| Minor | Suggestion, nice to have | "Consider renaming for clarity" |
| Nit | Trivial, stylistic | "Extra blank line here" |
Constructive Feedback Template
[Level] [Category]: [Issue]
**What:** [Describe the specific issue]
**Why:** [Explain why it matters]
**Suggestion:** [Offer a specific improvement]Example:
[Major] Correctness: Null reference possible
**What:** `user.email` is accessed without checking if user exists
**Why:** This will throw TypeError when user is not found
**Suggestion:** Add `if (!user) return null;` before accessing propertiesReview Checklist Summary
## Review: [PR Title]
### Stage 1: Requirements
- [ ] Implements requirements
- [ ] Handles edge cases
- [ ] Appropriate scope
### Stage 2: Correctness
- [ ] Logic is sound
- [ ] No bugs
- [ ] Errors handled
### Stage 3: Quality
- [ ] Readable
- [ ] Follows conventions
- [ ] Maintainable
### Stage 4: Testing
- [ ] Has tests
- [ ] Tests are good
### Stage 5: Security/Performance
- [ ] No vulnerabilities
- [ ] No performance issues
### Verdict: [ ] Approve [ ] Request Changes [ ] CommentIntegration with Other Skills
- planning/verification-gates: Review is a key gate
- testing/test-patterns: Evaluate test quality
- testing/anti-patterns: Spot testing issues
© rohitg00, 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
Just SKILL.md in packages/core/src/methodology/packs/collaboration/structured-review of rohitg00/skillkit.
Open the folder on GitHubat commit d2e5c34
Compare with similar skills
Structured 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 |
|---|---|---|---|---|---|---|
| Structured Code Review this skillrohitg00/skillkit | 1.5k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence | |
| Code Review Skillawesome-skills/code-review-skill | 2.1k | — | ~2.8k | Automated safety check: Notes | MIT | |
| Code Reviewerjewbetcha/opentrace | 116 | 2 repos | ~1.1k | Automated safety check: Notes | MIT | |
| Code Review SkillRain-kl/OpenFlare | 288 | — | ~2.3k | Automated safety check: Notes | MIT | |
| Code ReviewerYikai-Liao/symusic | 189 | 1 repos | ~1.3k | Automated safety check: Pass | MIT |
Similar skills
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…
Code Reviewer
jewbetcha/opentrace
Comprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go.
Code Review Skill
Rain-kl/OpenFlare
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, PHP, Python, Django, Go, C/.NET, Kotlin, Swift, NestJS, C/C++, and more.
Code Reviewer
Yikai-Liao/symusic
Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then…
Code Review Specialist
lhfer/claude-howto-zh-cn
Structured code review across security, performance, code quality and maintainability, with a checklist, a finding template and two Python scripts for complexity metrics.
More from rohitg00/skillkit
All 14 skills in this repoDesign First
rohitg00/skillkit
Guides the creation of technical design documents before writing code, producing architecture diagrams, data models, API interface definitions, implementation plans, and multi-option trade-off…
Find Skills
rohitg00/skillkit
Discovers, searches, and installs skills from multiple AI agent skill marketplaces (400K+ skills) using the SkillKit CLI.
Handoff Protocols
rohitg00/skillkit
Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating…
Hypothesis Testing
rohitg00/skillkit
Applies the scientific method to debugging by helping users form specific, testable hypotheses, design targeted experiments, and systematically confirm or reject theories to find root causes.
Parallel Investigation
rohitg00/skillkit
Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas.
Red Green Refactor
rohitg00/skillkit
Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green.
Related
Categories
Questions about Structured Code Review
What does Structured Code Review do?
Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Structured Code Review is an agent skill from rohitg00/skillkit. Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance.
When should I use Structured Code Review?
Structured Code Review fits situations like: the user asks for code review; pull request review; wants their code checked for bugs; vulnerabilities — triggered by phrases like review my code.
How do I install Structured Code Review in Claude Code?
Run `npx skills add rohitg00/skillkit --skill structured-code-review -a claude-code`. Or copy the skill folder (packages/core/src/methodology/packs/collaboration/structured-review in rohitg00/skillkit) into .claude/skills/structured-code-review in your project. Claude Code loads it when a task matches its description.
How do I install Structured Code Review in Codex?
Run `npx skills add rohitg00/skillkit --skill structured-code-review -a codex`. Or copy the skill folder (packages/core/src/methodology/packs/collaboration/structured-review in rohitg00/skillkit) into .agents/skills/structured-code-review in your project. Codex loads it when a task matches its description.
Can I use Structured 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 rohitg00/skillkit --skill structured-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/structured-code-review, .gemini/skills/structured-code-review, .github/skills/structured-code-review and .opencode/skills/structured-code-review in your project.
What does Structured Code Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Structured Code Review is instructions for the agent only.
Does Structured Code 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 Structured 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 Structured Code Review use?
Structured Code 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 Structured Code Review use?
About 1.3k tokens (SKILL.md is roughly 5k 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 Structured Code Review?
Skills that share tags, products or a category with Structured Code Review: WooCommerce Code Review (woocommerce/woocommerce, 11k stars), Code Review Skill (awesome-skills/code-review-skill, 2.1k stars), Code Reviewer (jewbetcha/opentrace, 116 stars) and Code Review Skill (Rain-kl/OpenFlare, 288 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Structured Code Review?
rohitg00 (a GitHub user) maintains it in rohitg00/skillkit, which has 1,546 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on June 2, 2026.
Source: rohitg00/skillkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.