rami-doctorlisted

Use when the user wants to diagnose, verify, or health-check a Rami install — "is Rami set up", "rami doctor", "check my rami install", "why isn't rami working". Runs read-only probes (MCP auth, GitHub App coverage, quota, plugin version) and prints a ✓/✗ checklist with the fix for each failure.
rami-code-review/claude-code-marketplace · ★ 0 · AI & Automation · score 62

Install: claude install-skill rami-code-review/claude-code-marketplace

# Rami Doctor Read-only diagnosis of a Rami install. Run every check, then print one checklist. Never mutate anything — no fixes are applied here; each failed check points at the command that fixes it. A failure in an early check (no MCP, no auth) makes later checks meaningless — mark those `skipped` rather than failed. ## Checks ### 1. MCP server connected Are the Rami MCP server's tools (`get_usage`, `get_current_branch_pr`, `get_review_results`, …) available? - Available → ✓ - Not available → ✗ **MCP server not connected.** Fix: `/rami:setup`, then `/mcp` → authenticate. ### 2. Authenticated ``` ReadMcpResource(uri="rami://auth/status") ``` - `authenticated: true` → ✓ (show `github_login`) - `authenticated: false` → ✗ **Not authenticated.** Fix: run `/mcp`, select `plugin:rami:rami`, press Enter to log in. This resource costs no quota. ### 3. GitHub App covers this repo ```bash REMOTE=$(git remote get-url origin) BRANCH=$(git branch --show-current) ``` Call `get_current_branch_pr(remote_url=$REMOTE, branch=$BRANCH)` on the Rami MCP server. - `status: success` → ✓ (App installed; PR `pr_url` found) - `status: auth_required` → ✗ **GitHub App not installed on this repo.** Fix: install it at https://github.com/apps/rami-code-remeow and scope it to this repo. - `status: not_found` → ⚠ App reachable, but **no open PR for `$BRANCH`** — push the branch and open a PR to use reviews. ### 4. Quota Call `get_usage()` on the Rami MCP server. - `can_execute_review: true`