aiskillstore/marketplace / skills/0xmsc/review-code
review-code
VerifiedProvides a structured workflow for planning and executing code reviews like a senior engineer. Use when asked to review code, PRs, or plan a code review task.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 785 B |
| references/checklist.md | markdown | 4.3 KB |
| skill-report.json | config | 9.8 KB |
skill-report.json
View on GitHub{
"schema_version": "2.0",
"meta": {
"generated_at": "2026-07-04T16:47:41.181Z",
"slug": "0xmsc-review-code",
"source_url": "https://github.com/0xmsc/coding_assistant/tree/master/src/coding_assistant/skills/review-code",
"source_ref": "master",
"model": "codex",
"analysis_version": "3.0.0",
"source_type": "community",
"content_hash": "69ecfa9a922f24307e4e435db9ba4fbe6d7481822d2cff6f592a6bc145921f92",
"tree_hash": "335a3c72f3301a918790171b1a5feef8c5dd872ea29cd31bf88c1690b34bb75b",
"provenance": {
"model_requested": "gpt-5.5:high",
"model_effective": "codex:gpt-5.5:high",
"fallback_chain": [
{
"agent": "codex",
"model": "gpt-5.5",
"effort": "high",
"outcome": "success"
}
],
"analysis_version": "3.0.0"
}
},
"skill": {
"name": "review-code",
"description": "Guides structured code reviews using a senior engineering workflow and checklist for quality, security, performance, and maintainability.",
"summary": "Guides structured PR and code reviews with a senior engineering checklist.",
"icon": "📦",
"version": "1.0.0",
"author": "0xmsc",
"license": "MIT",
"category": "coding",
"tags": [
"code-review",
"pull-request",
"security-review",
"testing",
"maintainability"
],
"supported_tools": [
"claude",
"codex",
"claude-code"
],
"risk_factors": [
"external_commands"
]
},
"security_audit": {
"risk_level": "safe",
"is_blocked": false,
"safe_to_publish": true,
"analysis_status": "ok",
"summary": "The static command execution findings are false positives caused by Markdown inline code in a prompt-only skill. No prompt injection, data exfiltration, or hidden execution intent was found in the reviewed files.",
"remediation": [],
"risk_factor_evidence": [
{
"factor": "external_commands",
"evidence": [
{
"file": "SKILL.md",
"line_start": 12,
"line_end": 12
},
{
"file": "SKILL.md",
"line_start": 17,
"line_end": 17
}
]
}
],
"static_findings": [
{
"id": "external_commands:SKILL.md:12:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 12,
"line_end": 12,
"snippet": "3. **Tools**: Run project-specific linting and testing commands (e.g., `just lint`, `npm test`, `pyt"
},
{
"id": "external_commands:SKILL.md:17:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 17,
"line_end": 17,
"snippet": "- `checklist.md`: Detailed review criteria."
}
],
"finding_verdicts": [
{
"id": "external_commands:SKILL.md:12:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.93,
"reason": "The backticked text is Markdown inline examples of common test and lint commands in a prompt-only skill. It does not execute commands or interpolate user input."
},
{
"id": "external_commands:SKILL.md:17:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.96,
"reason": "The backticks wrap a referenced Markdown filename in documentation. No executable code or command invocation is present."
}
],
"semantic_findings": [],
"critical_findings": [],
"high_findings": [],
"medium_findings": [],
"low_findings": [],
"dangerous_patterns": [],
"files_scanned": 2,
"total_lines": 115,
"audit_model": "codex",
"audited_at": "2026-07-04T16:47:41.181Z",
"agent_auto_install_policy": "allowed",
"manual_install_policy": "allowed"
},
"content": {
"user_title": "Review Code with a Senior Checklist",
"value_statement": "Code reviews can miss security, testing, and maintainability issues. This skill guides Claude, Codex, and Claude Code through structured review steps.",
"seo_keywords": [
"Claude",
"Codex",
"Claude Code",
"AI code review",
"pull request review",
"code review checklist",
"security review",
"test coverage review",
"maintainability review",
"senior engineer feedback"
],
"actual_capabilities": [
"Guides review scope discovery from tickets and pull request descriptions.",
"Uses a checklist for quality, security, performance, and maintainability.",
"Recommends project-specific linting, testing, and static analysis commands.",
"Structures feedback with rationale, severity, and suggested fixes.",
"Supports follow-up verification after fixes are made."
],
"limitations": [
"Does not execute tools by itself; the active assistant must run commands when available.",
"Depends on the context and diffs provided by the user or repository.",
"May miss issues outside the visible change set.",
"Does not replace project-specific reviewer judgment or domain requirements."
],
"use_cases": [
{
"title": "Review Pull Requests",
"description": "Use the checklist to find correctness, test coverage, security, and maintainability issues before merge.",
"target_user": "Software engineers"
},
{
"title": "Standardize Team Reviews",
"description": "Create consistent review expectations across a team and track follow-up verification after fixes.",
"target_user": "Engineering leads"
},
{
"title": "Check Solo Changes",
"description": "Check changes for common risks before release when another reviewer is not available.",
"target_user": "Open source maintainers"
}
],
"prompt_templates": [
{
"title": "Basic PR Review",
"prompt": "Review this change for correctness, tests, security, and maintainability. Return only actionable findings with severity and rationale.",
"scenario": "First review of a small pull request"
},
{
"title": "Checklist-Based Review",
"prompt": "Apply the review-code checklist to the current diff. Group findings by quality, security, performance, and maintainability.",
"scenario": "Structured review using the included checklist"
},
{
"title": "Release Readiness Review",
"prompt": "Review this release candidate for merge risk. Prioritize blocking issues, missing tests, rollback concerns, and follow-up verification steps.",
"scenario": "Pre-release review for a risky change"
},
{
"title": "Architecture-Focused Review",
"prompt": "Plan and execute a senior-level review of this design-heavy change. Evaluate coupling, cohesion, interfaces, error handling, and maintenance risk.",
"scenario": "Advanced review of broad architectural changes"
}
],
"output_examples": [
{
"input": "Review a small bug fix before merge.",
"output": [
"Summary: The change is focused and likely safe.",
"Finding: Add a regression test for the reported edge case.",
"Follow-up: Re-run the relevant unit tests after the fix."
]
},
{
"input": "Review a pull request that changes authorization logic.",
"output": [
"Summary: The change needs careful security review.",
"Finding: Confirm role checks cover both read and write paths.",
"Follow-up: Add tests for denied access and admin access."
]
}
],
"best_practices": [
"Provide the relevant diff, test results, and product context before requesting review.",
"Ask for severity labels when many findings are expected.",
"Run available tests and linters before asking for final approval."
],
"anti_patterns": [
"Do not ask for approval without sharing the changed files or diff.",
"Do not treat the checklist as a substitute for project requirements.",
"Do not ignore follow-up verification after fixes are applied."
],
"faq": [
{
"question": "Does this skill run commands automatically?",
"answer": "No. It recommends useful commands, but the active assistant or user must run available tools."
},
{
"question": "Can it review security changes?",
"answer": "Yes. The checklist includes validation, authorization, secrets, cryptography, error messages, and dependency risks."
},
{
"question": "Does it need a pull request?",
"answer": "No. It can review local diffs, copied code, or a planned change when enough context is provided."
},
{
"question": "Will it produce line-specific findings?",
"answer": "It can when file names and line numbers are available in the workspace or diff."
},
{
"question": "Can beginners use it?",
"answer": "Yes. The workflow gives a clear sequence: understand scope, apply the checklist, document findings, and verify fixes."
},
{
"question": "Which tools support it?",
"answer": "The report lists support for Claude, Codex, and Claude Code."
}
]
},
"file_structure": [
{
"name": "references",
"type": "dir",
"path": "references",
"children": [
{
"name": "checklist.md",
"type": "file",
"path": "references/checklist.md",
"lines": 98
}
]
},
{
"name": "SKILL.md",
"type": "file",
"path": "SKILL.md",
"lines": 17
}
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |