github

Automating GitHub issue and pull request management from your agent involves using this skill to list, create, update, review, and merge issues and PRs directly from your agent workspace. It reduces manual context switching and enables faster collaboration across organizations and personal accounts.

Yes, you can clone and manage GitHub repositories across multiple organizations and personal accounts using an agent. This skill applies to workflows that require repository management, branch control, and permission handling directly from the agent environment.

Yes, you need the GitHub CLI (gh) to manage branches and permissions from your agent workspace. This skill satisfies authentication via the gh CLI and uses environment token usage for secure operation during repository and pull request workflows.

Agent integration for creating and reviewing GitHub pull requests works by automating the workflow directly from the agent workspace. This allows you to create, list, update, review, and merge pull requests without manual context switching, applying to workflows across organizations.

The best way to handle GitHub access control and token authentication for automation is through repository-scoped access and environment token usage. This skill satisfies secure authentication via the GitHub CLI (gh) to manage branches and permissions safely.

Using an agent workspace for GitHub workflows automates repository, issue, and pull request management, reducing manual context switching. It enables faster collaboration by allowing you to clone repos, manage branches, and merge PRs across multiple accounts directly within your agent.