Github

Name: Github
Author: aws-samples

aws-samples/sample-strands-agent-with-agentcore

28 installs
186 repo stars
Updated August 4, 2026
aws-samples/sample-strands-agent-with-agentcore

github is a Claude skill that manages GitHub issues, PRs, branches, and repositories through OAuth-backed read and approval-gated write tools.

About

This skill gives an agent OAuth-backed access to GitHub for reading repos, issues, pull requests, and files, and for writing branches, file changes, and pull requests. Read operations include repo and code search; write operations are gated behind explicit user approval. A developer uses it when the assistant needs to inspect or modify GitHub repositories. It defers deep code analysis to a separate code agent.

Manages GitHub issues, PRs, branches, and repos via OAuth (3LO)
Read tools cover repo search, issues, pulls, file contents, and code search
Write tools (branch, push files, open PR) require explicit user approval

Github by the numbers

28 all-time installs (skills.sh)
Ranked #362 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
Data as of Aug 5, 2026 (Skillselion catalog sync)

At a glance

github capabilities & compatibility

Capabilities: pr management · issue tracking · code search
Works with: github
Use cases: code review
Pricing: Free

From the docs

What github says it does

Manage GitHub issues, PRs, branches, and repositories via OAuth (3LO).

SKILL.md

Never perform write operations autonomously.

SKILL.md

npx skills add https://github.com/aws-samples/sample-strands-agent-with-agentcore --skill github

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/aws-samples/sample-strands-agent-with-agentcore/github.svg)](https://skillselion.com/skills/aws-samples/sample-strands-agent-with-agentcore/github)

Installs	28
repo stars	★ 186
Last updated	August 4, 2026
Repository	aws-samples/sample-strands-agent-with-agentcore ↗

What it does

Let an agent read GitHub issues and PRs and, with approval, create branches, push files, and open pull requests.

Who is it for?

Reading GitHub issues, PRs, and files, and opening branches or pull requests from an agent after user approval.

Skip if: Deep code analysis, which the skill says to delegate to a code agent.

When should I use this skill?

The user needs to inspect or modify a GitHub repository, issue, or pull request.

What you get

GitHub issues/PRs read on demand and branches, file pushes, and pull requests created only with explicit approval.

GitHub branch
pushed file changes
pull request

By the numbers

8 read tools
3 approval-gated write tools

Files

SKILL.mdMarkdownGitHub ↗

GitHub

Available Tools

Read

github_search_repos(query, max_results?): Search GitHub repositories.
github_get_repo(owner, repo): Get repository details (description, stars, language, topics).
github_list_issues(owner, repo, state?, labels?, max_results?): List issues. state: open | closed | all.
github_get_issue(owner, repo, issue_number): Get a single issue with comments.
github_list_pulls(owner, repo, state?, max_results?): List pull requests.
github_get_pull(owner, repo, pull_number): Get a single pull request with diff summary.
github_get_file(owner, repo, path, ref?): Get file contents. ref defaults to default branch.
github_search_code(query, max_results?): Search code across GitHub (use repo:owner/name to scope).

Write (requires user approval)

github_create_branch(owner, repo, branch, from_branch?): Create a new branch.
github_push_files(owner, repo, branch, files, message): Create or update files. files: list of {path, content}.
github_create_pull_request(owner, repo, title, body, head, base?): Open a pull request.

Usage Guidelines

Never perform write operations autonomously. Only call github_create_branch, github_push_files, or github_create_pull_request when the user has explicitly requested or approved the action. If the user's intent is ambiguous, ask for confirmation before proceeding.
Always read existing files with github_get_file before modifying them.
Before calling any write tool, explain exactly what will change (branch name, target files, PR details) and wait for user agreement.
For multi-file changes: create a branch → push all files in one github_push_files call → open PR.
Use github_search_code with repo:owner/name qualifier to scope searches to a specific repository.

UI Guidance (from tools-config)

GitHub Tool Usage:

github_search_repos: Search GitHub repositories by keyword
github_get_repo: Get repository details (description, stars, language, topics)
github_list_issues: List issues (state: open|closed|all, filter by labels)
github_get_issue: Get a single issue with all comments
github_list_pulls: List pull requests
github_get_pull: Get a single PR with diff summary
github_get_file: Read file contents from a repo (specify ref/branch if needed)
github_search_code: Search code across GitHub (use repo:owner/name to scope)
github_create_branch: Create a new branch (write — requires approval)
github_push_files: Create or update files on a branch (write — requires approval)
github_create_pull_request: Open a pull request (write — requires approval)

Write workflow: 1. github_get_file to read existing files before modifying 2. github_create_branch to create a feature branch 3. github_push_files to commit all changes in one call 4. github_create_pull_request to open a PR