From patriotforge
Use when reviewing code changes, pull requests, or auditing existing code for compliance with PatriotForge conventions, security rules, and quality standards.
How this skill is triggered — by the user, by Claude, or both
Slash command
/patriotforge:code-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run through every category. Flag security violations as **🔴 CRITICAL**. Flag convention mismatches as **🟡 WARNING**.
Run through every category. Flag security violations as 🔴 CRITICAL. Flag convention mismatches as 🟡 WARNING.
extra='forbid' on all request schemaslocalStorage for secrets — HTTP-only cookies only/patriot-forge:security or read docs/SECURITY_RULES.mdRequest, Response, HTTPException)response_model and status_code on every endpointDepends() — no global stateany without justificationindex.ts per moduleforge_ table prefix on all new tablesNUMERIC(12,2) for money — never FLOATdeleted_at) — never hard deletecreated_at, updated_at timestamps on all tables# type: ignore without commentanyruff check and ruff format passmypy --strict passesbandit — no new findingsfix:, feat:, chore:, or refactor: prefixsed/awk in scripts — use Python for file editing📖 Cross-references: All other PatriotForge skills; docs/SECURITY_RULES.md
npx claudepluginhub aka-kolton/patriotforge-claude-plugin --plugin patriotforgeReview code systematically for security vulnerabilities using OWASP Top 10, secure coding patterns, and static analysis best practices. Use when reviewing pull requests, conducting security code reviews, or implementing secure development practices.
Audits code for OWASP Top 10 vulnerabilities, authentication flaws, security headers, and code quality (DRY/SOLID). Triggers on security-related terms.
Provides checklists for code reviews assessing correctness, security vulnerabilities, performance, and maintainability. Use for pull requests, audits, and feedback.