Source profileQuality 87/100

agentscope-ai/AgentTeams/manager/agent/worker-skills/github-operations/SKILL.md

github-operations

Use it for code review and operations tasks; the detail page covers purpose, installation, and practical steps.

Source repository stars
5,317
Declared platforms
0
Static risk flags
1
Last source update
2026-08-06
Source checked
2026-08-06

Decision brief

What it does—and where it fits

管理 GitHub Pull Request 和 Issue。包括创建/更新/合并 PR、添加评论、管理 Issue 等。注意:文件读写、分支操作、代码提交等请使用 git-delegation 技能。

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/agentscope-ai/AgentTeams --skill "manager/agent/worker-skills/github-operations"
    Safe inspection promptEditorial

    Inspect the Agent Skill "github-operations" from https://github.com/agentscope-ai/AgentTeams/blob/062f1c8d7edd54ceaa2141862dd98a75c36c6980/manager/agent/worker-skills/github-operations/SKILL.md at commit 062f1c8d7edd54ceaa2141862dd98a75c36c6980. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      How to Call GitHub Tools

      Use mcporter CLI to call MCP Server tools:

      Use mcporter CLI to call MCP Server tools:
    2. 02

      Create a review comment

      mcporter \ call mcp-github.createpullrequestreviewcomment --args '{ "owner": "higress-group", "repo": "agentteams", "pullnumber": 1, "body": "Consider using a helper function here.", "commitid": "'"$COMMITSHA"'", "path": "src/utils/helpers.ts", "line": 42, "side": "RIGHT" }' bas…

      createpullrequestreview: Has a template processing bug. For adding PR review comments, use:General PR comment: Use addissuecommentComment on specific code line: Use createpullrequestreviewcomment
    3. 03

      Typical Workflow

      1. Clone & modify → Use git-delegation skill 2. Push changes → Use git-delegation skill 3. Create PR → Use createpullrequest (this skill) 4. Review PR → Use addissuecomment, createpullrequestreviewcomment (this skill) 5. Merge PR → Use mergepullrequest (this skill)

      Clone & modify → Use git-delegation skillPush changes → Use git-delegation skillCreate PR → Use createpullrequest (this skill)
    4. 04

      Environment Variables

      No environment variables needed — mcporter reads its config from the default path ./config/mcporter.json automatically.

      No environment variables needed — mcporter reads its config from the default path ./config/mcporter.json automatically.
    5. 05

      Method 1: key=value format (recommended for simple args)

      mcporter \ call mcp-github. key1=value1 key2=value2

      mcporter \ call mcp-github. key1=value1 key2=value2

    Permission review

    Static risk signals and limitations

    Reads files

    low · line 303

    The documentation asks the agent to read local files, directories, or repositories.

    call mcp-github.search_issues q="is:issue is:open repo:agentscope-ai/AgentTeams"

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score87/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars5,317SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    agentscope-ai/AgentTeams
    Skill path
    manager/agent/worker-skills/github-operations/SKILL.md
    Commit
    062f1c8d7edd54ceaa2141862dd98a75c36c6980
    License
    Apache-2.0
    Collected
    2026-08-06
    Default branch
    main
    View the original SKILL.md

    GitHub PR & Issue Management

    Overview

    This skill allows you to manage Pull Requests and Issues via the centralized MCP Server. For git operations (clone, pull, push, commit, branch), use the git-delegation skill instead.

    Environment Variables

    No environment variables needed — mcporter reads its config from the default path ./config/mcporter.json automatically.

    TaskUse This SkillUse git-delegation
    Create/update/close PR
    Review/merge PR
    Comment on PR/Issue
    Create/update/close Issue
    Clone repository
    Pull/fetch changes
    Read/write files
    Create branches
    Commit/push code

    How to Call GitHub Tools

    Use mcporter CLI to call MCP Server tools:

    # Method 1: key=value format (recommended for simple args)
    mcporter \
      call mcp-github.<TOOL_NAME> key1=value1 key2=value2
    
    # Method 2: JSON format with --args flag (for complex objects)
    mcporter \
      call mcp-github.<TOOL_NAME> --args '{"key1":"value1","key2":"value2"}'
    

    IMPORTANT:

    • Always place --config BEFORE the call subcommand
    • For JSON arguments, use the --args flag (not bare JSON string)
    • Use mcp-github.<tool_name> selector format

    Output

    mcporter returns JSON output. Parse with jq for clean results.


    Pull Request Operations

    create_pull_request

    Create a new Pull Request:

    mcporter \
      call mcp-github.create_pull_request --args '{
        "owner": "higress-group",
        "repo": "agentteams",
        "title": "Add new feature",
        "body": "## Summary\n- Change 1\n- Change 2\n\n## Test plan\n- [ ] Test A\n- [ ] Test B",
        "head": "feature-branch",
        "base": "main"
      }'
    

    list_pull_requests

    List PRs in a repository:

    mcporter \
      call mcp-github.list_pull_requests owner=higress-group repo=agentteams state=open
    

    get_pull_request

    Get details of a specific PR:

    mcporter \
      call mcp-github.get_pull_request owner=higress-group repo=agentteams pull_number=1
    

    update_pull_request

    Update PR title, body, or state:

    mcporter \
      call mcp-github.update_pull_request --args '{
        "owner": "higress-group",
        "repo": "agentteams",
        "pull_number": 1,
        "title": "Updated title",
        "body": "Updated description"
      }'
    

    merge_pull_request

    Merge a PR:

    mcporter \
      call mcp-github.merge_pull_request owner=higress-group repo=agentteams pull_number=1 merge_method=squash
    

    get_pull_request_files

    List files changed in a PR:

    mcporter \
      call mcp-github.get_pull_request_files owner=higress-group repo=agentteams pull_number=1
    

    get_pull_request_status

    Get CI status of a PR:

    mcporter \
      call mcp-github.get_pull_request_status owner=higress-group repo=agentteams pull_number=1
    

    request_reviewers

    Request reviewers for a PR:

    mcporter \
      call mcp-github.request_reviewers --args '{
        "owner": "higress-group",
        "repo": "agentteams",
        "pull_number": 1,
        "reviewers": ["reviewer-username"]
      }'
    

    PR Comments & Reviews

    add_issue_comment (general PR comments)

    Add a general comment to a PR (PRs are also issues):

    mcporter \
      call mcp-github.add_issue_comment owner=higress-group repo=agentteams issue_number=1 body="LGTM! Great work."
    

    list_issue_comments

    List comments on a PR:

    mcporter \
      call mcp-github.list_issue_comments owner=higress-group repo=agentteams issue_number=1
    

    create_pull_request_review_comment

    Comment on a specific code line in a PR:

    # First get the latest commit SHA from the PR
    PR_DATA=$(mcporter \
      call mcp-github.get_pull_request owner=higress-group repo=agentteams pull_number=1)
    COMMIT_SHA=$(echo "$PR_DATA" | jq -r '.head.sha')
    
    # Create a review comment
    mcporter \
      call mcp-github.create_pull_request_review_comment --args '{
        "owner": "higress-group",
        "repo": "agentteams",
        "pull_number": 1,
        "body": "Consider using a helper function here.",
        "commit_id": "'"$COMMIT_SHA"'",
        "path": "src/utils/helpers.ts",
        "line": 42,
        "side": "RIGHT"
      }'
    

    get_pull_request_comments

    List all review comments on a PR:

    mcporter \
      call mcp-github.get_pull_request_comments owner=higress-group repo=agentteams pull_number=1
    

    get_pull_request_reviews

    List reviews on a PR:

    mcporter \
      call mcp-github.get_pull_request_reviews owner=higress-group repo=agentteams pull_number=1
    

    Issue Operations

    create_issue

    Create a new issue:

    mcporter \
      call mcp-github.create_issue owner=higress-group repo=agentteams title="Bug report" body="Description..."
    

    list_issues

    List issues in a repository:

    mcporter \
      call mcp-github.list_issues owner=higress-group repo=agentteams state=open
    

    get_issue

    Get details of a specific issue:

    mcporter \
      call mcp-github.get_issue owner=higress-group repo=agentteams issue_number=1
    

    update_issue

    Update issue title, body, state, or labels:

    mcporter \
      call mcp-github.update_issue --args '{
        "owner": "higress-group",
        "repo": "agentteams",
        "issue_number": 1,
        "title": "Updated title",
        "state": "closed"
      }'
    

    add_issue_comment

    Add a comment to an issue:

    mcporter \
      call mcp-github.add_issue_comment owner=higress-group repo=agentteams issue_number=1 body="Comment text"
    

    list_issue_comments

    List comments on an issue:

    mcporter \
      call mcp-github.list_issue_comments owner=higress-group repo=agentteams issue_number=1
    

    Labels

    list_labels

    List labels in a repository:

    mcporter \
      call mcp-github.list_labels owner=higress-group repo=agentteams
    

    get_label

    Get details of a label:

    mcporter \
      call mcp-github.get_label owner=higress-group repo=agentteams name=bug
    

    Search Operations

    search_issues

    Search issues and PRs:

    mcporter \
      call mcp-github.search_issues q="is:issue is:open repo:agentscope-ai/AgentTeams"
    

    search_code

    Search code in repositories:

    mcporter \
      call mcp-github.search_code q="function handleAuth repo:agentscope-ai/AgentTeams"
    

    search_repositories

    Search repositories:

    mcporter \
      call mcp-github.search_repositories query="agentteams language:go"
    

    search_users

    Search users:

    mcporter \
      call mcp-github.search_users q="john location:shanghai"
    

    Utility Operations

    get_me

    Get current authenticated user:

    mcporter \
      call mcp-github.get_me
    

    list_notifications

    List notifications:

    mcporter \
      call mcp-github.list_notifications all=false
    

    list_teams

    List teams in an organization:

    mcporter \
      call mcp-github.list_teams
    

    list_team_members

    List members of a team:

    mcporter \
      call mcp-github.list_team_members org=higress-group team_slug=core-team
    

    Known Issues

    • create_pull_request_review: Has a template processing bug. For adding PR review comments, use:
      • General PR comment: Use add_issue_comment
      • Comment on specific code line: Use create_pull_request_review_comment

    Important Notes

    • Transport: The MCP Server uses HTTP transport (configured in mcporter-servers.json)
    • Auth: HTTP endpoint requires Authorization header with Bearer token (auto-configured)
    • Rate limits: GitHub API rate limits apply. If you get 403 responses, wait and retry
    • Permissions: Your MCP access is controlled by the Manager. If you get 403 from the MCP Server, the Manager may need to re-authorize your access

    Typical Workflow

    1. Clone & modify → Use git-delegation skill
    2. Push changes → Use git-delegation skill
    3. Create PR → Use create_pull_request (this skill)
    4. Review PR → Use add_issue_comment, create_pull_request_review_comment (this skill)
    5. Merge PR → Use merge_pull_request (this skill)

    Alternatives

    Compare before choosing

    Computed 9723,881

    alirezarezvani/claude-skills

    adversarial-reviewer

    Adversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.

    Computed 9688,665

    ruvnet/RuView

    github-code-review

    Comprehensive GitHub code review with AI-powered swarm coordination

    Computed 954,969

    dotnet/skills

    grade-tests

    Grades a specified set of test methods individually and produces a concise table mapping each test (fully-qualified name) to a letter grade (A–F), a score band, and a one-line note — designed to be posted as a PR comment. Use when the caller wants per-test feedback on a curated list of methods (for example, the new or modified tests in a pull request), not a suite-wide audit. Polyglot: .NET, Python, TS/JS, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, C++. Input is a list of test methods (or

    Computed 951,319

    daymade/claude-code-skills

    github-review-pr

    Reviews or re-reviews one contributor pull request—including an explicitly named closed PR being reconsidered—or a bounded newest-to-oldest sweep of all open contributor PRs, for a GitHub repository maintainer against the current base branch. Handles base drift, history discontinuities, polluted branches, ownership, curation, supersession, and review-conditioned repair or landing using immutable Git snapshots, three-way merge results, isolated contribution projection, checks, tests, and findings