review

Solid

Multi-agent code review of GitHub Pull Requests (Python source, documentation (Markdown/RST), and CI/CD config PRs) covering architecture, tests, performance, docs, lint, security, and API design. TRIGGER when: user provides a GitHub PR number (e.g. 42, #42) and asks to review/audit/check it, or provides a saved review-report path with --reply to draft a contributor-facing comment; phrases: 'review PR 123', 'audit this pull request', 'look at PR #42', 'draft a reply for this review report'. SKIP: local file or current git diff review (use /develop:review (requires 'develop' plugin)); non-Python source PRs without Python files (TypeScript-only, Go-only, Rust-only); standalone issue/discussion thread analysis (use /oss:analyse).

Code & Development 23 stars 3 forks Updated yesterday Apache-2.0

Install

View on GitHub

Quality Score: 87/100

Stars 20%
46
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

<objective> Spawn specialized sub-agents in parallel. Consolidate findings into structured feedback with severity levels. NOT for local file review or current git diff — use `/develop:review` (requires `develop` plugin). NOT for non-Python source PRs (TypeScript, Go, Rust, etc.) unless they include Python files — docs-only and CI/CD-only PRs in scope. NOT for standalone GitHub issue analysis or thread summarization — use `oss:analyse`. **Draft PRs** (GitHub `isDraft=true`) are work-in-progress; pass explicit PR number anyway to review draft. Note: oss:review performs inline linked-issue analysis (root-cause alignment check in Step 1) as part of PR review — within scope, no conflict. </objective> <inputs> - **$ARGUMENTS**: PR number or report path. - Number given (e.g. `42` or `#42`): review PR diff - `--reply`: spawn oss:shepherd to draft contributor-facing PR comment. Path ending in `.md` → spawn oss:shepherd from that report, skip new review. - **Scope**: Python source only. Non-Python file → state out of scope, suggest tool, no findings. - **Local files**: use `/develop:review` (requires `develop` plugin) for local files or current git diff. - `--codemap`: strict mode — stop, report if codemap not installed (on by default when installed; use `--no-codemap` to opt out; requires codemap plugin installed) - `--semble`: enable semble semantic search companion (off by default; requires semble MCP server configured) - **--plan handoff not supported** — skill doe...

Details

Author
Borda
Repository
Borda/AI-Rig
Created
5 months ago
Last Updated
yesterday
Language
Python
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

review

Review, audit, sanity-check, look-at any review-able target. Triggers on a GitHub PR URL (fetched via the gh CLI), a local path or "." (review the working tree), a markdown/doc file, or a comment-thread URL. Read-only by default; --fix applies accepted findings locally and pushes to the PR branch after confirmation (never force, never merge, never to a protected branch). Produces severity-tiered findings (blocker / critical / should / may / nit) with path:line and <=15-word verbatim evidence quotes. Six dimensions: correctness, tests, security, performance, readability, consistency. For a deep PR review with cross-file code-context retrieval, use /adk:pr-review.

0 Updated 5 days ago
sujeet-pro
Code & Development Solid

review-github-pr

GitHub PR code review - fetches the diff, runs automated checks, launches 3 parallel review agents (correctness, convention compliance, efficiency) to analyze changes, validates findings against actual code, and drafts a GitHub review. Use when reviewing pull requests. Triggers on "review this PR", "review PR

31 Updated 3 days ago
tenequm
Code & Development Solid

code-review

Review code changes using context-aware multi-agent pipeline with severity-based findings. TRIGGER when: user asks to review code, analyze PR quality, check for issues, run code review, or audit changes (e.g., "코드 리뷰해줘", "review this PR", "코드 분석해줘", "리뷰 돌려줘"). DO NOT TRIGGER when: user is replying to review comments (use review-reply), creating PRs, committing, or performing git operations without review intent.

7 Updated today
chanmuzi