Loading...
Loading...
Found 4 Skills
Run vet immediately after ANY logical unit of code changes. Do not batch your changes, do not wait to be asked to run vet, make sure you are proactive.
Audit test coverage for code changes. Identifies untested logic and provides specific test recommendations. Read-only analysis. Use before PR or after implementation. Triggers: review coverage, check tests, test coverage, are tests adequate.
Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch/PR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.
Multi-AI Cross-Review Workflow. Conduct cross-reviews of code changes between different AI tools (Claude, Codex, Gemini, etc.). Trigger scenarios: When users call /discuss-multi-ai, mention asking other AIs to review changes, or post a review request containing a commit hash. This skill should also be triggered even if users simply say "Help me generate review text for another AI" or "Send this change to other AIs for review."