What it does
Expert code review of current git changes with a senior engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements.
Skills ZICQ category:Security code-review-expert
Expert code review of current git changes with a senior engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements.
Official URL:skills.sh
Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.
Expert code review of current git changes with a senior engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements.
The official description does not include a separate “Use when”. Per the spec, agents activate this skill when the task matches keywords in that description.
Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Code Review Expert; Overview; Severity Levels; Workflow; 1) Preflight context; 2) SOLID + architecture smells. It includes spec-recommended sections: step-by-step instructions.
File analysis: besides SKILL.md, the body references references/solid-checklist.md, references/removal-plan.md, references/security-checklist.md, references/code-quality-checklist.md. Those resources load on demand.
Code Review ExpertOverviewSeverity LevelsWorkflow1) Preflight context2) SOLID + architecture smells3) Removal candidates + iteration plan4) Security and reliability scan5) Code quality scan6) Output formatCode Review SummaryFindings
Source category:skills.sh agent-skill
namecode-review-expertdescriptionreferences/solid-checklist.mdreferences/removal-plan.mdreferences/security-checklist.mdreferences/code-quality-checklist.mdThese paths are extracted from the text. Check the upstream package to verify the files exist.
Invocation syntax and available tools depend on your Agent client. Client integration guide ↗
Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.
This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.
Copy these instructions to a compatible agent and confirm the target directory matches your client.
Install the agent skill "code-review-expert" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-8aec857694a79d1f-Code-Review-Expert.html Save it as .cursor/skills/code-review-expert/SKILL.md or .claude/skills/code-review-expert/SKILL.md and keep the frontmatter name and description exactly as-is. This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/sanyuan0704/sanyuan-skills instead of creating only a SKILL.md.
Requires Node.js and npx. First inspect the repository's skill list to confirm the name.
npx skills add 'https://github.com/sanyuan0704/sanyuan-skills' --list
npx skills add 'https://github.com/sanyuan0704/sanyuan-skills' --skill 'code-review-expert'
The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.
Perform a structured review of the current git changes with focus on SOLID, architecture, removal candidates, and security risks. Default to review-only output unless the user asks to implement changes.
| Level | Name | Description | Action | |-------|------|-------------|--------| | P0 | Critical | Security vulnerability, data loss risk, correctness bug | Must block merge | | P1 | High | Logic error, significant SOLID violation, performance regression | Should fix before merge | | P2 | Medium | Code smell, maintainability concern, minor SOLID violation | Fix in this PR or create follow-up | | P3 | Low | Style, naming, minor suggestion | Optional improvement |
git status -sb, git diff --stat, and git diff to scope changes.rg or grep to find related modules, usages, and contracts.Edge cases:
git diff is empty, inform user and ask if they want to review staged changes or a specific commit range.references/solid-checklist.md for specific prompts.references/removal-plan.md for template.references/security-checklist.md for coverage.references/code-quality-checklist.md for coverage.Structure your review as follows:
## Code Review Summary
**Files reviewed**: X files, Y lines changed
**Overall assessment**: [APPROVE / REQUEST_CHANGES / COMMENT]
---
## Findings
### P0 - Critical
(none or list)
### P1 - High
1. **[file:line]** Brief title
- Description of issue
- Suggested fix
### P2 - Medium
2. (continue numbering across sections)
- ...
### P3 - Low
...
---
## Removal/Iteration Plan
(if applicable)
## Additional Suggestions
(optional improvements, not blocking)
Inline comments: Use this format for file-specific findings:
::code-comment{file="path/to/file.ts" line="42" severity="P1"}
Description of the issue and suggested fix.
::
Clean review: If no issues found, explicitly state:
After presenting findings, ask user how to proceed:
---
## Next Steps
I found X issues (P0: _, P1: _, P2: _, P3: _).
**How would you like to proceed?**
1. **Fix all** - I'll implement all suggested fixes
2. **Fix P0/P1 only** - Address critical and high priority issues
3. **Fix specific items** - Tell me which issues to fix
4. **No changes** - Review complete, no implementation needed
Please choose an option or provide specific instructions.
Important: Do NOT implement any changes until user explicitly confirms. This is a review-first workflow.
| File | Purpose |
|------|---------|
| solid-checklist.md | SOLID smell prompts and refactor heuristics |
| security-checklist.md | Web/app security and runtime risk checklist |
| code-quality-checklist.md | Error handling, performance, boundary conditions |
| removal-plan.md | Template for deletion candidates and follow-up plan |
Security
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, p…
Security
MoltGuard — OpenClaw security guard by OpenGuardrails. Install MoltGuard to protect you and your human from prompt injection, data exfiltrat…
Security
Use when reviewing code for security vulnerabilities, implementing authentication flows, auditing OWASP Top 10, configuring CORS/CSP headers…
Security
Security vetting protocol before installing any AI agent skill. Red flag detection for credential theft, obfuscated code, exfiltration. Risk…