agentleFS
mir-ammir-am/skills-agents-ai-coding/skills/gh-copilot-review/SKILL.md

gh-copilot-review

Skill2 starsChanged 43 days agoMITView on GitHub

Request a GitHub Copilot review for a pull request via gh CLI

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 3 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user wants to request a GitHub Copilot review on a pull request.

    line 20
  2. Very specific:

    If given only a PR number, the current repository must have a GitHub origin remote

    line 25
  3. Very specific:

    If gh not installed -> error: Error: GitHub CLI not found.

    line 27
  4. Very specific:

    If not authenticated -> error: Error: Not authenticated with GitHub.

    line 28
  5. Very specific:

    If input is a full PR URL, use it directly with gh pr view <pr>.

    line 41
  6. Distinctive:

    If input is a PR number, resolve the repository from git remote get-url origin.

    line 42
  7. Very specific:

    If the input is neither a valid URL nor a PR number, error with Error: Provide a GitHub PR URL or PR number.

    line 43
  8. Very specific:

    No GitHub remote for PR number mode -> Error: No GitHub remote found.

    line 84
  9. Very specific:

    Use gh CLI for all interactions

    line 92
  10. Distinctive:

    Do not use this skill for file-scoped or comment-driven Copilot prompts

    line 94

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

What I do

  • Accept a GitHub pull request URL or PR number
  • Validate GitHub CLI (gh) access and PR visibility
  • Request a standard GitHub Copilot review for the whole PR
  • Return a concise result with the PR URL

When to use me

Use this skill when the user wants to request a GitHub Copilot review on a pull request.

Prerequisites

  • GitHub CLI (gh) v2.88.0 or later must be installed and authenticated
  • If given only a PR number, the current repository must have a GitHub origin remote
  • The target PR must be accessible with the current GitHub credentials
  • If gh not installed -> error: Error: GitHub CLI not found. Install: https://cli.github.com/
  • If not authenticated -> error: Error: Not authenticated with GitHub. Run: gh auth login

Input Handling

Accept either of these forms:

  • Full GitHub PR URL
    • Example: https://github.com/owner/repo/pull/123
  • PR number
    • Example: 123

Resolution rules:

  1. If input is a full PR URL, use it directly with gh pr view <pr>.
  2. If input is a PR number, resolve the repository from git remote get-url origin.
  3. If the input is neither a valid URL nor a PR number, error with Error: Provide a GitHub PR URL or PR number.

Workflow

  1. Validate GitHub access
    gh auth status
  2. Resolve PR metadata
    • For PR URL:
      gh pr view <pr> --json number,title,url,author,baseRefName,headRefName
    • For PR number in current repo:
      git remote get-url origin
      gh pr view <number> --json number,title,url,author,baseRefName,headRefName
  3. Request Copilot review for the full PR
    gh pr edit <pr> --add-reviewer @copilot
    
    # or, for PR number in the current repository
    gh pr edit <number> --add-reviewer @copilot
  4. Report results
    Requested GitHub Copilot review for PR #123.
    - Mode: Added @copilot as reviewer via gh CLI
    - PR: https://github.com/owner/repo/pull/123

Error Handling

  • Invalid input -> Error: Provide a GitHub PR URL or PR number
  • gh missing -> Error: GitHub CLI not found. Install: https://cli.github.com/
  • gh too old -> Error: GitHub CLI v2.88.0+ is required for @copilot reviewer requests
  • Not authenticated -> Error: Not authenticated with GitHub. Run: gh auth login
  • No GitHub remote for PR number mode -> Error: No GitHub remote found. Provide a full PR URL or set origin
  • PR not found or inaccessible -> Error: Unable to access the pull request with current GitHub credentials
  • Reviewer add failed -> Error: Unable to add @copilot as a reviewer on this pull request
  • Copilot unavailable for repository or plan -> Error: GitHub Copilot review is not available for this repository or account

Notes

  • This skill requests a PR-wide Copilot review only
  • Use gh CLI for all interactions
  • This skill uses native reviewer support through gh pr edit --add-reviewer @copilot
  • Do not use this skill for file-scoped or comment-driven Copilot prompts

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.