lov-gh-access

# lov-gh-access Grant, revoke, and audit collaborator access on private GitHub repos — by username **or** email, with read-only as the safe default. ## Prerequisites - `gh` CLI authenticated (`gh auth status`) with a token that has: - `repo` scope (always) - `admin:org` scope (if the target repo is org-owned; caller must be org owner or repo admin) - The target repo exists and is accessible to the caller. ## Subcommands This skill has three modes. Pick based on the user's intent: | User intent | Subcommand | |---|---| | "开权限 / share / invite / grant" | **grant** | | "撤销 / remove / revoke / 踢出" | **revoke** | | "谁有权限 / who has access / list" | **list** | If intent is unclear, use `AskUserQuestion` to disambiguate. ## Workflow ### Step 0: Collect inputs via AskUserQuestion **ALWAYS** collect the following BEFORE touching the API: 1. **Target repo** — `<owner>/<repo>` (e.g. `skill-publisher/private-demo`). If the user is inside a git repo, pre-fill from `gh repo view --json nameWithOwner -q .nameWithOwner`. 2. **Subcommand** — grant / revoke / list. 3. **(grant/revoke only) Identifiers** — a whitespace- or comma-separated list of GitHub usernames and/or email addresses. Mixed is fine. 4. **(grant only) Permission level** — default `pull` (read-only). Offer: - `pull` — read + issues + PRs (recommended default) - `triage` — read + can label/close issues & PRs, no code write - `push` — write access (⚠ confirm explicitly) - `maintain` / `admin` — blo...