copilot-spaces

Load curated GitHub Copilot Spaces context into conversations for grounded responses.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BrunoAMSilva/my-config --skill copilot-spaces-brunoamsilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copilot-spaces
Source: https://github.com/BrunoAMSilva/my-config/tree/main/coding/skills/copilot-spaces
Command: npx skills add https://github.com/BrunoAMSilva/my-config --skill copilot-spaces-brunoamsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Copilot Spaces brings curated, project-specific documentation, code, and instructions into conversations so answers and generated content are grounded in the team's actual knowledge and repositories. It eliminates guesswork and reduces the risk of producing guidance that conflicts with project conventions or outdated docs.

Core Features & Use Cases

  • List available Copilot Spaces accessible to a user and present relevant matches for selection.
  • Load a Space's full context (documentation, files, custom instructions) to answer questions, follow workflows, generate code, or draft docs that adhere to team standards.
  • Use GitHub CLI (gh api) for creating, updating, and deleting spaces when writes are required, and use MCP read endpoints for safe, read-only retrieval.
  • Use Case: Onboard a new engineer by loading the project's Space containing architecture docs, coding standards, and templates so the assistant can produce compliant code samples and checklists.

Quick Start

Load the Accessibility copilot space and answer questions using its documentation and templates.

Frequently Asked Questions about copilot-spaces

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

FAQPage Schema
How do I load project-specific context into GitHub Copilot conversations?

To load project-specific context into GitHub Copilot conversations, you can use Copilot Spaces to aggregate repository files, documentation, and issues. This grounds assistant responses in your team's actual knowledge and coding standards.

Can I generate code that adheres to team coding standards using GitHub repository files?

Yes, you can generate code adhering to team standards by loading a Space's full context, including custom instructions and repository files. This ensures generated content aligns with established project conventions and documentation.

Do I need GitHub API access to retrieve Copilot Spaces context for answering questions?

Yes, retrieving Copilot Spaces context requires either MCP GitHub read endpoints for safe read-only retrieval or GitHub CLI (gh api) access with owner and name identifiers to list, load, and aggregate project resources.

What's the best way to onboard engineers using project documentation and architecture docs?

The best way to onboard engineers is loading a project Space containing architecture docs and templates. This allows the assistant to produce compliant code samples and checklists grounded in the team's actual knowledge base.

Can I create and update Copilot Spaces using the GitHub CLI?

Yes, you can create, update, and delete Copilot Spaces using the GitHub CLI (gh api) when write operations are required. MCP read endpoints are used separately for safe, read-only retrieval of Space context.

Why does my generated code conflict with outdated project documentation?

Generated code conflicts with outdated documentation when conversations lack project-specific grounding. Loading a curated Copilot Space eliminates guesswork and reduces the risk of producing guidance that conflicts with current project conventions.