Evidence-based investigative code review using deductive reasoning to determine what actually happened versus what was claimed. Use when verifying implementation claims, investigating bugs,...
Retrieval practice session to test retention on a topic. Use when user wants to test their knowledge, practice recall, quiz themselves, or check what they remember. Triggers on "quiz me", "test my...
codereview / code review / 代码审查 - Go 代码审查技能，专注于性能、并发安全、安全性和可读性四大核心维度。
Use when receiving code review feedback, before implementing suggestions,
Comprehensive GitHub code review with AI-powered swarm coordination
Comprehensive GitHub code review with AI-powered swarm coordination
Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability
Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability
Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability
Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability
Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability
Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability
Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability
Post PR review comments using the GitHub API with inline comments, suggestions, and priority labels.
A comprehensive code review skill that analyzes code for best practices, potential bugs, security issues, and suggests improvements.
Conducts a comprehensive security review of a git repo. Use when asked about security issues, code quality concerns, or to evaluate the security posture of a codebase or library.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not...
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not...
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not...
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not...