Skills matching the name, description or GitHub author.
GitHub development workflow best practices. Use when creating commits, pull requests, branches, reviewing code, managing issues, or any git/GitHub operations. Provides standards for commit messages, PR descript...
Orchestrates complex or architectural code changes through a structured workflow. Use when the user requests multi-file changes, new features, architectural refactoring, database schema changes, new API endpoin...
This skill should be used when the user asks to "провести ревью", "проверить код", "найти проблемы в коде", "code review", "найти баги", "проверить на ошибки", "analyze code quality", "ревью PR", "review pull r...
Use when executing implementation plans with independent tasks in the current session or facing 3+ independent issues that can be investigated without shared state or dependencies - dispatches fresh subagent fo...
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Fe...
Comprehensive GitHub code review with AI-powered swarm coordination
Expert code review for Python, microservices, security, and production best practices. Automatically activated when code review is needed to identify bugs, security issues, and quality problems.
Monitor PR for code review, analyze feedback with AI, implement fixes, and merge when approved with CI green.
Monitor PR for code review, analyze feedback with AI, implement fixes, and merge when approved with CI green.
Monitor PR for code review, analyze feedback with AI, implement fixes, and merge when approved with CI green.
Multi-agent code review orchestration following 2024-2025 best practices. Use when: - Reviewing code changes before commit or merge - PR review with comprehensive analysis needed - Security audit of code change...
How to track our work through commits, pull-requests, and pushes. Maintain proper git hygiene in our chaotic, multi-agent environment through atomic commits, with the option to have code reviewed by AI agents w...
Code Reviewer Agent. Frontend/Backend 코드 리뷰를 담당합니다. 코드 품질, 테스트 커버리지, 보안, 성능을 검토합니다.
Use when interacting with GitHub repositories, branches, or PRs. Automatically triggered for PR viewing, code review, and repo inspection tasks.
Complete code review workflow for PR/MR with multiple reviewers and automated checks. Triggers: PRW, 審查流程, review workflow, PR review, MR review, pull request, merge request, 程式碼審查流程, full review, 完...
Create AI-assisted code reviews on GitHub, GitLab, or Forgejo. Use when asked to review a PR/MR, analyze code changes, or provide review feedback.
Code review workflow for evaluating changes against standards. Use when reviewing pull requests, commits, or diffs.
Technical evaluation of code review feedback. Use when receiving review feedback - requires verification before implementing, no performative agreement, push back when technically wrong.
Multi-agent spec review with parallel Claude/OpenCode reviewers. Use after spec-create or standalone via /spec.review.
Orchestrate multi-agent development workflows. Use when starting a new feature to coordinate architecture design, implementation, code review, and release through specialized sub-agents.
Follow project-wide development conventions for file structure, documentation, version control, environment configuration, and code review processes. Use this skill when organizing project files and directories...
Use for security, quality, and PM compliance review before merging strategy code. Supports Ralph Loop iterative mode for backtest optimization. Runs PM audit, security audit, code review, backtest validation, a...
Automated TFVC code review for Azure DevOps changesets with Snyk security scanning and Notion integration
Phased Implementation Supervisor to coordinate coding and code review subagents. Use this skill when the user has an implentation plan file and wants to execute it phase by phase with build verification, testin...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.