gh-agent-session

Create and manage GitHub Copilot agent sessions via gh agent-task.

4.9k|489|Updated Aug 12, 2025
One-click install
npx skills add https://github.com/github/gh-aw --skill gh-agent-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-agent-session
Source: https://github.com/github/gh-aw/tree/main/skills/gh-agent-session
Command: npx skills add https://github.com/github/gh-aw --skill gh-agent-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The GitHub CLI Agent Session Extension streamlines automated, auditable code changes by turning natural language instructions into GitHub Copilot-driven agent sessions that create and manage pull requests.

Core Features & Use Cases

  • Create agent sessions via gh agent-task to initiate automated code changes from plain language descriptions.
  • List, view, and update existing sessions across repositories, enabling cross-repo workflow automation.
  • Leverage safe-outputs and authentication controls to govern when and how agent-driven changes are applied.

Quick Start

Install the agent-task extension and start a session with a descriptive task: gh extension install github/agent-task gh agent-task create "Refactor authentication flow" gh agent-task view 123

Frequently Asked Questions about gh-agent-session

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull requests with GitHub Copilot from natural language?

You can automate pull requests by creating GitHub Copilot agent sessions that translate natural language instructions into automated code changes using the gh agent-task extension.

What are GitHub Copilot agent sessions and how do they work?

GitHub Copilot agent sessions are automated workflows that process plain language task descriptions to generate, manage, and submit code changes via pull requests.

How do I manage cross-repo automation tasks with GitHub Copilot agents?

You can list, view, and update existing agent sessions across multiple repositories using the gh agent-task extension to handle cross-repo workflow automation.

Do I need a PAT to use gh agent-task for workflow automation?

Yes, authenticating with appropriate PAT permissions is required to govern how and when agent-driven changes are applied and to ensure secure automation.

How do I control safe-outputs when automating code changes with Copilot agents?

You leverage safe-outputs and authentication controls within the gh agent-task extension to govern when and how agent-driven changes are securely applied.

What are the limitations of using GitHub Copilot agent sessions for issue resolution?

Limitations include requiring the specific gh CLI extension installation and appropriate PAT permissions, meaning you must configure safe-outputs carefully to prevent unauthorized automated changes.