code-reviewer
Review Code for Security and Quality
Complex changes can hide security bugs, reliability issues, and maintainability risks. This skill guides Claude, Codex, and Claude Code through structured review workflows.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "code-reviewer" from https://skillstore.io/skills/sickn33-code-reviewer.md and its manifest at https://skillstore.io/api/skills/sickn33-code-reviewer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "code-reviewer". Review a new login flow before merge.
Expected outcome:
- High: Session invalidation is missing after password reset.
- Medium: Login failure logs include user identifiers without retention guidance.
- Low: Add tests for expired token and repeated failure cases.
Using "code-reviewer". Assess a database migration for production risk.
Expected outcome:
- Medium: The migration may lock a large table during peak traffic.
- Recommendation: Split the schema change from the backfill and add progress monitoring.
- Follow-up: Confirm rollback behavior before deployment.
Using "code-reviewer". Review a service endpoint for performance.
Expected outcome:
- Medium: The endpoint performs repeated queries for each returned item.
- Recommendation: Batch related lookups and add timing metrics.
- Test gap: Add a high-volume request case.
Security Audit
SafeBoth static findings are false positives after context review. The backtick pattern is only Markdown inline formatting around a resource path, and the network reconnaissance match points to a team collaboration heading.
Risk Factors
⚙️ External commands (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-code-reviewer/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-code-reviewer?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-code-reviewer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-code-reviewer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-code-reviewer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). code-reviewer security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-code-reviewer/audits/4BibTeX citation
@techreport{sickn33-sickn33-code-reviewer-2026,
author = {sickn33},
title = {code-reviewer security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-code-reviewer/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "code-reviewer security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/sickn33-code-reviewer/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-code-reviewer:audit:4"
description: "Skillstore immutable audit report identifier"
Compare variants
9 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
alirezarezvani-code-reviewer
2026-08-21
autumnsgrove-code-reviewer
2026-08-21
davila7-code-reviewer
2026-08-21
curiouslearner-code-reviewer
2026-08-21
sickn33-code-reviewer
2026-08-21
9tykeshav-code-reviewer
2026-08-21
dennisliuck-code-reviewer
2026-08-21
google-gemini-code-reviewer
2026-08-21
shubhamsaboo-code-reviewer
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Review Pull Requests
Assess a proposed change for bugs, security issues, missing tests, and production risks before merge.
Assess Security-Sensitive Code
Review authentication, authorization, input validation, secrets handling, and API behavior for exploitable weaknesses.
Improve Release Readiness
Evaluate configuration, observability, migrations, deployment scripts, and rollback plans before a production release.
Try These Prompts
Review this change for correctness, security, tests, and maintainability. List findings by severity with concise remediation steps.
Review this code for security issues. Focus on input validation, access control, secrets, injection risks, logging, and unsafe defaults.
Review this implementation for performance and reliability risks. Check database behavior, caching, concurrency, timeouts, retries, and resource limits.
Act as a release gate reviewer. Evaluate security, reliability, migration safety, observability, rollback readiness, tests, and operational impact.
Best Practices
- Provide the full diff, relevant tests, and expected behavior before review.
- Ask for severity-ranked findings with evidence and concrete remediation.
- Include deployment context when reviewing migrations, infrastructure, or configuration.
Avoid
- Do not ask for a broad approval without sharing code or requirements.
- Do not ignore low-severity maintainability issues that can grow into technical debt.
- Do not use review feedback as a replacement for tests or security scanning.