ousiass/code-review-en
skills/code-review-en/SKILL.md
Full codebase quality check and refactoring review with report generation.
development
Updated May 6, 2026
$ install --global
skillsauthnpx skillsauth add ousiass/claude-config code-review-enInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 6, 2026, 6:14 AM137.2s1 file scanned
SKILL.md
- name:
- code-review-en
- description:
- Full codebase quality check and refactoring review with report generation.
- user-invocable:
- true
Language: Always interact with the user in 日本語.
code-review-en
Prerequisites
- Claude Code environment
ghCLI (for GitHub Issue output)
Arguments
- No arguments: Check the entire project in the current directory
- Path specified: Check only the specified directory or file
Phase 1: Project Structure Analysis
- Identify directory structure, languages, and frameworks
- Determine frontend / backend / both
- List target files (exclude
.gitignoreentries and build artifacts) - Identify applicable check criteria and create tasks with TaskCreate
Phase 2: Quality Check
Run all applicable check criteria based on the detected project structure. Check all target files. Split by directory if there are many files.
Check criteria details in:
- Common:
references/check-common.md - Linterly:
references/check-linterly.md - Frontend:
references/check-frontend.md(includes Atomic Design rules) - Backend:
references/check-backend.md - Refactoring:
references/check-refactoring.md
Phase 3: Report Generation
- Confirm output destination with
AskUserQuestion:- GitHub Issue (recommended): Title
review: Code quality report (<branch>, <YYYY-MM-DD>) - Local MD file:
code-review-report.md - Console output: Print the report directly in the conversation
- GitHub Issue (recommended): Title
- Use report format from
templates/report.md - Report summary to user
Severity Criteria
| Severity | Criteria | |----------|----------| | Critical | Security risk, data loss, production incident | | Important | Architecture violation, missing layer separation, untestable structure | | Suggestion | Readability/maintainability improvements, refactoring candidates | | Minor | Naming improvements, code style, trivial improvements |
Rules
- Never report based on guesses. Verify against actual code
- Always include file path and line number in findings
- Provide concrete improvement suggestions
- Always include Critical/Important findings. Include Suggestion/Minor only if clear benefit
- Respect framework conventions and existing code style
- Track progress with TaskCreate/TaskUpdate
Related Skills
ousiass/test-plan
testing
VerifiedTrustedCommunity
PRのTest planチェックリストからローカル実行用テスト手順書を生成しPRコメントに投稿
SKILL.mdUpdated May 6, 2026
ousiass/stitch-shopify
content-media
VerifiedTrustedCommunity
Stitchモックzipを展開しShopify OS 2.0テーマ（Atomic Design snippets構造）に変換する
SKILL.mdUpdated May 6, 2026
ousiass/stitch-deploy
devops
VerifiedTrustedCommunity
Stitchモックzipを展開しNetlifyデプロイ可能な構造に変換する
SKILL.mdUpdated May 6, 2026
ousiass/spec-to-hugo
development
VerifiedTrustedCommunity
既存の仕様書ディレクトリをHextraテーマのHugo仕様書サイトに変換する
SKILL.mdUpdated May 6, 2026