Key Enterprise copilot features that would be amazing #205849
Unanswered
MikkelRavnsted
asked this question in
Copilot Conversations
Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Copilot Agentic Workflows
Body
Enterprise-Wide Agentic Infrastructure for GitHub Copilot
Context
As an AI Architect operating within a GitHub Enterprise environment, my team leverages multiple AI platforms — with GitHub Copilot serving as the primary tool for our engineering teams. Through ongoing work to improve cross-team collaboration around AI tooling, I have identified two feature gaps that I believe would significantly enhance how enterprises scale agentic capabilities across their organizations.
Feature Request 1: Centralized Agentic Library
Background
GitHub already supports a
.github-privaterepository as a mechanism for sharing custom agents across an Enterprise. This is a strong foundation — however, its current scope is limited to custom agents only.Proposal
Extend the
.github-privaterepository (or introduce a dedicated equivalent) to function as a centralized agentic library — a single, authoritative source for all agentic resources across the organization or enterprise.This library would host:
agent.md— Custom agentsskill.md— Reusable skillsprompt.md— Shared prompts*.instructions.md— Shared instruction setsExpected Behavior
All members within the organization or enterprise would have seamless access to every resource in the library — directly from their IDE or CLI — without any manual setup or cloning.
Example: A skill published to the centralized library would be immediately available via:
in Copilot Chat or the CLI.
Value
When a high-quality, reusable skill or prompt is developed anywhere within the enterprise, it can be promoted to the centralized library and instantly made available to every team — eliminating duplication of effort and accelerating adoption of best practices.
Feature Request 2: Enterprise-Wide Reusable Agentic Workflows
Background
Agentic workflows are rapidly maturing, and teams across enterprises are investing heavily in building sophisticated, high-value workflows. Sharing and reusing these workflows across teams, however, remains unnecessarily difficult.
As a concrete example: I developed an agentic workflow that analyzes other agentic workflows from an architectural perspective and provides structured improvement feedback. This workflow is robust and broadly applicable — but making it available to others across our enterprise in a frictionless way is not currently possible.
The existing alternatives all have significant drawbacks:
Proposal
Introduce the concept of a Reusable Agentic Workflow — a designation that can be applied to any repository within an organization or enterprise via settings.
When a repository is marked as a Reusable Agentic Workflow, it registers a new slash-command available to all members of the org or enterprise within their IDE and CLI.
Example: My architectural review workflow would register as:
Expected Behavior
When the slash-command is invoked:
/fix,/explain).Value
This would enable enterprise teams to publish, discover, and invoke high-quality agentic workflows in the same way they consume any other built-in Copilot capability — significantly lowering the barrier to reuse and cross-team collaboration.
Summary
Both proposals share a common principle: agentic assets should be first-class, enterprise-distributable resources — discoverable and usable directly from the developer's IDE or CLI, without operational overhead.
.github-privateto host all agentic resource types, accessible via slash-commandsAll reactions