Loading...
Loading...
Found 1,259 Skills
Reviews watchOS code for app lifecycle, complications (ClockKit/WidgetKit), WatchConnectivity, and performance constraints. Use when reviewing code with import WatchKit, WKExtension, WKApplicationDelegate, WCSession, or watchOS-specific patterns.
Professional Skills and Methodologies for Secure Code Review
Use this skill when conducting or improving code reviews. Provides structured review processes, conventional comments patterns, language-specific checklists, and feedback templates. Use when reviewing PRs or standardizing review practices.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Comprehensive GitHub code review with AI-powered swarm coordination
Perform automated code reviews on GitLab merge requests. Analyzes code for style, bugs, security, performance, and error handling issues. Generates HTML report for easy reading.
Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"
Automated code review and analysis. Use when: user wants to review code changes, check for issues, analyze complexity, or perform security scans.
Code review staged changes or a specific area of the codebase, optionally delegating to a chosen agent. Use when the user wants a code review.
Use when reviewing code, pull requests, patches, CLs, diffs, or proposed implementations for engineering quality, code health, design, functionality, tests, maintainability, specialist risk, or approval risk. TRIGGER on "review this PR", "code review", "LGTM?", "approve?", "is this code/diff/change safe to merge/deploy?", and local diff reviews. DO NOT TRIGGER for PR descriptions, PR splitting, author review-feedback responses, or non-code safety questions unless code review is requested.
Provides automated, context-aware code reviews focusing on logic errors and style violations. Use during Pull Request cycles to identify potential bugs and maintain high code quality standards.
Use this skill after completing multiple, complex software development tasks before informing the user that work is complete.