trove-security-review
Security review skill that checks code for common vulnerabilities. Covers OWASP Top 10, secret detection, and secure coding patterns.
- License 许可
- MIT
- 所属仓库
- bravew/trove
- 最近更新
- 2026-11-12
- Stars
- ★ 10
- Forks
- 1
01 前言 Front Matter
- name
- trove-security-review
- metadata
- { "trove-category": "it-security", "trove-category-label": "IT & security" }
- description
- Security review skill that checks code for common vulnerabilities. Covers OWASP Top 10, secret detection, and secure coding patterns.
- when_to_use
- security review; owasp check; vulnerability audit
02 资源文件 1
- 其他SKILL.md.tmpl2.0 KB
03 SKILL.md 正文
<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --> <!-- Regenerate: bun run build:skills -->
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
Security Review Guidelines
OWASP Top 10 Checklist
1. Injection (SQL, NoSQL, Command)
- All queries use parameterized statements
- User input is never concatenated into queries/commands
- ORM methods are preferred over raw queries
2. Broken Authentication
- Passwords hashed with bcrypt/argon2 (not MD5/SHA1)
- Session tokens are cryptographically random
- Failed login attempts are rate-limited
3. Sensitive Data Exposure
- Secrets stored in env vars / secret managers (never in code)
- PII is encrypted at rest
- HTTPS enforced for all endpoints
4. Broken Access Control
- Authorization checked on every endpoint
- Users can only access their own resources
- Admin endpoints have explicit role checks
5. Security Misconfiguration
- CORS origins are explicitly listed (not
*) - Debug mode is disabled in production
- Default credentials are changed
Secret Detection Patterns
Flag any occurrences of:
- API keys, tokens, passwords in source code
.envfiles committed to git- Hardcoded connection strings with credentials
- Private keys or certificates in repos
For systematic secret detection across the whole tree, hand off to
trove-secret-scan — it's this skill's benefits-from for that
specific reason. Use it as a delegated, bounded sub-agent (input:
"scan everything under src/ for secret patterns"; expected output:
file:line + pattern type or "clean"). See
docs/orchestration.md for delegation
phrasing.
Output Format
## Security Review
### 🔴 Critical Vulnerabilities
- [file:line] [CWE-XXX] Description and fix
### 🟡 Security Warnings
- [file:line] Description and recommendation
### ✅ Security Positives
- Good practices observed
04 同仓库更多 Skills
using-trove
Skill discipline anchor for the Trove marketplace. Loaded once per session; routes the agent to the right trove-* skill before code, planning, review, or git actions.
trove-write-skill
Skill authoring workflow. Use when creating or updating a Codex or Trove skill, including rubrics, tasks, metadata, and validation.
trove-worktree
Git worktree workflow for spikes, risky experiments, and broad refactors that should not disturb the user's current branch.
trove-why
Reconstruct design rationale and decision history from evidence — source control, issue tracker (Linear), docs (Notion), chat (Slack), error tracking (Sentry) — with calibrated confidence. Use for "why does X work this way", "why did we pick Y", regressions, and postmortems. Use trove-explain for how it works now.
trove-verify
Completion verification workflow. Use before claiming done, fixed, complete, ready, or shipped.
trove-unslop
Cut AI tells from writing — PR descriptions, release notes, specs, commit bodies, and replies. Use before finalizing prose, or when the user asks to clean up, de-slop, or make text sound human.