← ClaudeAtlas

reviewlisted

Review a GitHub PR or GitLab MR with craft-level attention to semantic HTML, CSS architecture, accessibility, TypeScript patterns, and code quality. Auto-detects platform from URL or git remote. Proposes inline diff comments, shows them for approval, only posts what the user approves. TRIGGER when the user says "/abc:review", "review this PR/MR", "review <url>", or passes a PR/MR number.
semanticpixel/abc · ★ 0 · Code & Development · score 76
Install: claude install-skill semanticpixel/abc
# /abc:review Review a GitHub **pull request** or GitLab **merge request** with craft-level attention to semantic HTML, CSS architecture, accessibility, TypeScript patterns, and code quality. Auto-detects platform. Proposes inline diff comments, shows them for approval, posts only what the user approves. **Input:** `$ARGUMENTS` --- ## Phase 0 — Detect platform and parse input ### Determine platform Platform detection in order: 1. **URL with `github.com`** → `platform = github` 2. **URL with `gitlab.` host** (e.g. `gitlab.com`, self-hosted GitLab) → `platform = gitlab` 3. **Bare number** (e.g. `123`) → resolve the remote URL, then apply rules 1–2 against it. Check `git remote get-url upstream` **first** (fork workflows push the PR/MR to the canonical `upstream` repo, not the contributor's `origin` fork); fall back to `git remote get-url origin` if no `upstream` remote exists. If cwd is not in a git repo, or neither remote resolves → ask the user for a URL. 4. **No arguments** → ask for the PR/MR URL or number. 5. **Neither pattern matched** (an argument was passed but it's neither a recognizable URL nor a bare number, e.g. a branch name or freeform text) → terminal fallback: use `AskUserQuestion` to ask the user for the PR/MR URL or number directly. Do not guess. Once platform is determined, verify CLI auth: - GitHub: `gh auth status` — if not authed, surface the exact command and stop. - GitLab: the MCP tools handle their own auth; if a call fails with auth errors, su