codereview
Deep code review skill for Go code focusing on performance, security, concurrency safety, and readability. Supports reviewing local uncommitted code, recent commits, or specified commits/branches/tags.
ai-comm
Cross-AI CLI communication for Kitty terminal. Use when collaborating with other AI assistants (Codex, Gemini, Aider, Cursor, OpenCode), delegating tasks, or requesting code review.
security-review
Security review checklist for code changes. Automatically activates when reviewing security-sensitive code, authentication, authorization, or data handling.
reviewing-code
>-
receiving-code-review
>-
collaborating-with-coco
Delegates coding tasks to Coco CLI (Codebase Copilot) for prototyping, debugging, and code review. Use when needing algorithm implementation, bug analysis, or code quality feedback. Supports multi-turn sessions via SESSION_ID.
coderabbit-fix-flow
This skill should be used when CodeRabbit code review feedback needs to be processed and fixed systematically. Use after running `coderabbit --plain` to automatically save feedback, analyze issues using MCP tools, and implement minimal code fixes with proper planning.
executing-ai-development-workflow
Execute a comprehensive AI-driven development workflow with planning, implementation, multi-layer review (Sub-agents + /review + CodeRabbit CLI), automated fixes, and PR creation. Use when implementing new features, performing large refactorings, developing security-critical features, or when the user mentions "AI開発ワークフロー", "AI development workflow", or "計画的に実装".
feature-pr-fixing
Use when addressing PR review comments - follow structured workflow
feature-pr-reviewing
Use when reviewing pull request changes - follow structured workflow
detecting-ai-code
Use when auditing code for AI authorship, reviewing acquisitions/contractors, verifying academic integrity, or during code review - provides systematic tiered framework for detecting fully AI-generated AND AI-assisted code patterns with confidence scoring
pr-review
Reviews code changes before merging. Use when reviewing PRs, checking staged changes, reviewing diffs, code review, merge readiness check, or validating changes before commit/push.
best-practices-extractor
Extract and generate coding best practices from PR review comments. Use when you want to analyze PR comments from a repository to create best practices documentation, or update existing standards with new feedback. Triggers include "extract best practices from repo X", "analyze PR comments", "update coding standards", or "generate best practices from PRs".
code-compliance
Validate code against established best practices during code reviews. Use when checking if code follows team standards, during /4_review workflow, or for pre-commit validation. Triggers include "check code compliance", "validate against best practices", "does this follow our standards", or automatically invoked by /4_review command.
audit
Validates research/plan/code against overengineering, underengineering, and hallucination
code-review
Code reviewer focusing on correctness, regressions, security, and test coverage - P0/P1/P2 severity
subagent-driven-development
Use when executing implementation plans. Dispatches independent subagents for individual tasks with code review checkpoints between iterations for rapid, controlled development.
code-review-checklist
Apply comprehensive code review checklist covering purpose, design, quality, correctness, security, performance, testing, and documentation. Use when reviewing pull requests, conducting code reviews, or self-reviewing changes before committing.
Page 4 of 10 · 173 results