GitHub setup guide

GitHub setup starts
with your goal.

Start in Copilot CLI with one prompt. The agent checks your current setup and asks for decisions it cannot resolve by inspecting GitHub.

Install the plugin →Start your plan

Install once

Use GitHub Copilot CLI, signed in to your Copilot account. Install GitHub CLI (gh) and jq, then authenticate gh to the intended GitHub host. The enterprise must already exist.

After this package is published, install the plugin from your terminal. You do not need to clone the curriculum or register an MCP server.

copilot plugin marketplace add microsoft/frontier-agentic-devops-rvas
copilot plugin install github-enterprise-setup@frontier-agentic-devops
copilot skill list

Check that github-enterprise-setup appears under the plugin source. Open a new Copilot session from the directory where you want to work:

copilot

To update the plugin, run these commands in your terminal:

copilot plugin marketplace update frontier-agentic-devops
copilot plugin update github-enterprise-setup

To remove the plugin:

copilot plugin uninstall github-enterprise-setup

Preview. Packaging and offline workflow checks are tested. Complete a controlled live setup before production use.

Describe the setup you need

Replace the placeholders below and send this prompt in Copilot. Use github.com or your enterprise's full ghe.com hostname.

Use the github-enterprise-setup skill to set up enterprise <enterprise-slug>
on <host>, covering organizations <org-slugs>.
My goal is <outcome>. Assess current state and recommend changes.
Ask only for unresolved decisions. Save a plan without changing GitHub.

For the outcome, describe the result you need, such as aligning organization governance or setting up team and repository access.

The skill starts in Plan mode. It checks the target and active identity, then gathers evidence without changing GitHub. Inventories within your requested scope do not need another skill-level approval. Copilot's tool permissions still apply.

The agent recommends changes and asks you to resolve one decision at a time. Its questions depend on your target and goal. It reuses values you supplied or that it verified through GitHub.

Review before requesting Apply

Read plan.md. Check the target, proposed changes, verification checks, and any cost or license effects. Those operations must wait until you meet the prerequisites and other owners finish their required work.

When the plan matches your decisions, tell the agent:

Proceed with the reviewed plan. Present the first write batch for approval.

This requests Apply; it does not approve a write. Review and approve each batch. High-impact changes need a separate typed confirmation. The agent asks before switching accounts or changing authentication scopes.

Continue saved work

In the same conversation, ask the agent to continue. It reuses the known target and run directory. In a new conversation, supply the full path:

Use the github-enterprise-setup skill to resume the run at <absolute-run-path>.
Recheck identity and live state before continuing.

On resume, the skill checks the saved files and verifies any writes whose outcome is uncertain before continuing. Changes to the target or effects need new approval. Keep unverified work separate from completed operations.

Get recommendations without a change plan

Use the github-enterprise-setup skill in Assess mode for enterprise
<enterprise-slug> on <host>, covering <scope>. Report gaps and prioritized
recommendations. Do not create a change plan or change GitHub.

Assess stops after the report. Ask to continue into Plan when you want to turn selected recommendations into proposed changes.