code-review
Security-focused code review before committing
Works with
---
name: code-review
description: Security-focused code review before committing
license: MIT
---
# Security Code Review
Review code changes for security issues before committing.
## Purpose
This skill performs a security-focused code review to catch common vulnerabilities before they make it into the codebase. Run this before committing to self-check your changes.
## Security Checklist
When reviewing code, check for:
### Secrets & Credentials
- [ ] No hardcoded secrets (API keys, passwords, tokens)
- [ ] No AWS credentials in code
- [ ] No private keys or certificates
- [ ] Environment variables used for sensitive config
### Injection Vulnerabilities
- [ ] No SQL injection (use parameterized queries)
- [ ] No command injection (avoid shell=True, sanitize inputs)
- [ ] No LDAP injection
- [ ] No XPath injection
### Input Validation
- [ ] No path traversal (validate file paths)
- [ ] No open redirects
- [ ] User input properly sanitized
- [ ] File uploads validated
### Dependencies
- [ ] Dependencies are from trusted sources
- [ ] No wildcard version specifications
- [ ] Lock files present and updated
### General Security
- [ ] File permissions are appropriate
- [ ] No debug code left in
- [ ] Error messages don't leak sensitive info
- [ ] Logging doesn't include sensitive data
## Usage
```
/code-review
```
Run this skill before committing to perform a self-check on your changes.
## Output
The skill will:
1. Identify changed files using `git diff`
2. Review each file against the security checklist
3. Report any findings with severity levels
4. Provide remediation suggestions
## Example Findings
```
[HIGH] src/api.py:42 - Hardcoded API key detected
→ Move to environment variable: os.getenv('API_KEY')
[MEDIUM] src/db.py:15 - SQL query uses string formatting
→ Use parameterized query: cursor.execute("SELECT * FROM users WHERE id = ?", (user_id,))
[LOW] src/utils.py:8 - Debug print statement
→ Remove before committing
```More Code Review skills
pr-to-video
heygen-com/hyperframes
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.
receiving-code-review
obra/superpowers
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
public-relations
coreyhaines31/marketingskills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.

