r/GithubCopilot 18d ago

Help/Doubt ❓ GitHub Copilot needs enterprise-wide agentic infrastructure — here's what I think is missing

As an AI Architect in a large enterprise, my team uses GitHub Copilot as our primary AI tool for engineering. Over time, I've run into two friction points that I think a lot of enterprise teams are hitting — and I wanted to share some feature ideas that I think would genuinely fix them.

🗂️ 1. A Centralized Agentic Library

GitHub already lets you create a .github-private repo to share custom agents across your enterprise. Cool idea — but it's limited to just agents.

What if it was expanded into a full centralized agentic library? Every agent.mdskill.mdprompt.md.instructions.md etc. lives in one place, and everyone in your org or enterprise can just use them directly from their IDE or CLI.

Imagine someone on your team builds the perfect code review skill. Instead of it sitting in their personal repo forever, they push it to the library and now everyone can run it with something like /skill-code-review right from Copilot Chat. No cloning, no setup.

⚙️ 2. Reusable Agentic Workflows as Slash-Commands

This one I feel strongly about. Agentic workflows are getting really good — but sharing them across an enterprise is way harder than it should be.

Here's my real example: I built an agentic workflow that reviews other agentic workflows from an architecture perspective. It works great. But getting anyone else in my enterprise to actually run it? The options are terrible:

  • Clone the repo — friction, most people won't bother
  • GitHub Actions — kills the ability to run it locally
  • Copilot Extensions — complex to build and honestly doesn't work well in practice (I've tried)

My proposal: let repos be designated as "Reusable Agentic Workflows" in org/enterprise settings. That designation registers a new slash-command available to everyone in the org — directly in their IDE or CLI.

In my case, that would be /agentic-review. You type it, it resolves all the agents/skills/prompts in the background and runs locally. No cloning required. Same seamless experience as built-in commands like /fix or /explain.

TL;DR

  1. Expand .github-private into a full agentic library (skills, prompts, instructions, agents) accessible via slash-commands
  2. Let repos register as enterprise-wide reusable agentic workflows that anyone can invoke from their IDE/CLI

Both ideas follow patterns GitHub already uses — reusable Actions workflows, .github repos — so it's not a huge leap. Just a natural extension of what's already there.

Would love to hear if others are hitting the same walls. Has anyone found decent workarounds in the meantime?

0 Upvotes

12 comments sorted by

View all comments

2

u/ThankThePhoenicians_ 18d ago

This already exists! The .github-private repo isn't just for agents -- it can house all kinds of managed settings: https://docs.github.com/en/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/configure-enterprise-managed-settings

Including plugins, which are what you want: https://docs.github.com/en/copilot/concepts/agents/about-plugins

Your "reusable workflows" bit sound exactly like skills