\r \r

Code and System Security Review\r

\r Report only real risks, not manufactured panic.\r \r

Use Cases\r

\r Triggers when users request a security review, code audit, security check, vulnerability analysis, security assessment, penetration test, code scan, or security review.\r \r

Workflow\r

\r

1. Identify trust boundaries, user inputs, privileged operations, and sensitive data paths.\r
2. Focus on checking for injection, path traversal, XSS, insecure deserialization, authentication and authorization flaws, key leaks, insecure logging, and command execution issues.\r
3. Assess both exploitability and impact scope; do not exaggerate low-confidence issues.\r
4. Mark risks with clear severity levels: critical, high, medium, low.\r
5. Provide directly actionable remediation recommendations; prioritize providing code patches when possible.\r
6. If the risk cannot be fully closed in this round, explain the residual risk and subsequent checkpoints.\r \r

Output Format\r

\r For each risk point, output:\r \r

• Risk Point: Brief description of the issue's location and nature\r
• Risk Level: critical | high | medium | low\r
• Impact Description: Actual consequences if exploited\r
• Remediation Plan: Specific, actionable steps to fix the issue\r
• Patch: A code diff that can be directly applied (prioritize providing this)\r \r When no risks are found, output a brief confirmation and do not fabricate issues.\r \r

Common Vulnerability Checklist\r

\r See references/checklist.md for details, covering the OWASP Top 10 and common attack surfaces.