security-review · relatedb — Claude Code security skill: review and install
The security-review Claude Code skill reviews code changes for security risks and suggests remediations. It activates for auth or permission changes, secrets and PII handling, public endpoints, and dependency upgrades.
Apache-2.0 ★ 423 updated 2026-11-16
npx skills add relatedb/relate --skill security-review -a claude-codeWhat security-review does
security-review guides a review of entry points, data flows, and trust boundaries, then checks likely threats and common weaknesses. Its checklist covers input validation, output encoding, paths and URLs, access control, secrets, personal data, and dependency changes.
For issues such as unsafe SQL, commands run with untrusted input, or overly broad roles, the skill proposes a minimal safe fix and tests to guard against regressions. Review commands must be read-only, so the skill should not modify project files.
What it helps with
- review access control after auth changes
- spot secrets exposed in logs or configuration
- assess a new public endpoint for security risks
- check how user input and URLs are handled
- review the risks of a dependency upgrade
Example prompts for the agent
- Review these authorization changes for security issues.
- Threat-model the new public endpoint.
- Run a security review after the dependency upgrade.
How to install security-review
1Skills CLI (Vercel)
npx skills add relatedb/relate --skill security-review -a claude-code2Manually: put the files in place
~/.claude/skills/security-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/security-review/
1Skills CLI (Vercel)
npx skills add relatedb/relate --skill security-review -a codex2Manually: put the files in place
.agents/skills/security-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add relatedb/relate --skill security-review -a cursor2Manually: put the files in place
.cursor/skills/security-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install relatedb/relate .agents/skills/security-review2Manually: put the files in place
.github/skills/security-review/SKILL.md1Skills CLI (Vercel)
npx skills add relatedb/relate --skill security-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/relatedb/relate --path .agents/skills/security-reviewManually: put the files in place
.devin/skills/security-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add relatedb/relate --skill security-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about security-review
How do I install security-review in Claude Code?
Run npx skills add relatedb/relate --skill security-review -a claude-code. The skill file is at ~/.claude/skills/security-review/SKILL.md.
What does security-review do?
It guides security reviews by examining data flows and trust boundaries, then checking areas such as authorization, input handling, secrets, and dependencies. It can suggest fixes and regression tests for identified issues.
Does security-review modify project files?
No. Its review commands should be read-only, and the skill should not change files.
Source text
SKILL.md · Apache-2.0
--- name: security-review description: A specialist skill for security reviews, threat modeling, and remediation guidance. Use for auth/permissions changes, secrets or PII handling, public endpoints, or dependency upgrades. --- # Security Review Skill ## Tooling Notes This skill should only use read-only commands and avoid modifying files. ## Workflow Copy this checklist and use it to track your progress through a security review: ```markdown Security Review Checklist - [ ] Scope the Change - [ ] Identify entry points, data flows, and trust boundaries. - [ ] Note any changes to auth, secrets, or external integrations. - [ ] Threat Model - [ ] Enumerate likely threats (STRIDE or similar). - [ ] Focus on inputs, storage, and outputs. - [ ] Validate Input & Output - [ ] Validate and sanitize user-controlled input. - [ ] Encode outputs to prevent injection. - [ ] Constrain file paths and URLs (avoid traversal/SSRF). - [ ] AuthN/AuthZ - [ ] Authentication checks are present and consistent. - [ ] Authorization rules are explicit and least-privilege. - [ ] Session/token handling uses secure defaults. - [ ] Secrets & PII - [ ] No hardcoded secrets or credentials. - [ ] Logs avoid sensitive data. - [ ] Storage and transport are protected. - [ ] Dependency Risk - [ ] New dependencies are minimal and justified. - [ ] Lockfiles updated and reviewed. - [ ] Verification - [ ] Add or update tests for security-sensitive behavior. - [ ] Confirm error handling does not leak data. ``` # Security Guardrails ## Review Focus Areas - Authentication and authorization checks are explicit and consistent. - Input validation is present on all user-controlled data. - Secrets and credentials never appear in logs or configs. - Public endpoints enforce rate limits and safe defaults. - Dependencies are minimized and vetted for risk. ## Common Red Flags - New endpoints without authN/authZ checks. - Raw SQL, command execution, or templating with unsanitized input. - Hardcoded secrets, tokens, or private keys. - Broad permissions or wildcard roles. ## Remediation Notes When issues are found, propose the smallest safe change that addresses the risk, then add or update tests to prevent regressions.
© relatedb · Apache-2.0 · relatedb/relate
Similar skills
All skills for Security →security-review by other authors comes first.