Code review, debugging, architecture, testing and docs. 100 reviewed prompts for engineering.
Maps how a feature or system you own could be attacked or misused and lists prioritized defenses, detection and tests. Use during design or before a security review of your own product.
Reviews an infrastructure-as-code change and its plan output for destroyed or replaced resources, leaked secrets, blast radius and version drift, then gives a validation and rollback plan. Use it before applying changes to shared environments.
Standing approach for reviewing code: rank findings by impact, explain why, and suggest a fix. Use when asked to review code, a change or a pull request.
Reviews a Python snippet for missing docs, style, type hints and slow patterns, then returns an improved version with a change list. Use it before sharing or merging a script.
