Close Menu
    DevStackTipsDevStackTips
    • Home
    • News & Updates
      1. Tech & Work
      2. View All

      CodeSOD: A Unique Way to Primary Key

      July 22, 2025

      BrowserStack launches Figma plugin for detecting accessibility issues in design phase

      July 22, 2025

      Parasoft brings agentic AI to service virtualization in latest release

      July 22, 2025

      Node.js vs. Python for Backend: 7 Reasons C-Level Leaders Choose Node.js Talent

      July 21, 2025

      The best CRM software with email marketing in 2025: Expert tested and reviewed

      July 22, 2025

      This multi-port car charger can power 4 gadgets at once – and it’s surprisingly cheap

      July 22, 2025

      I’m a wearables editor and here are the 7 Pixel Watch 4 rumors I’m most curious about

      July 22, 2025

      8 ways I quickly leveled up my Linux skills – and you can too

      July 22, 2025
    • Development
      1. Algorithms & Data Structures
      2. Artificial Intelligence
      3. Back-End Development
      4. Databases
      5. Front-End Development
      6. Libraries & Frameworks
      7. Machine Learning
      8. Security
      9. Software Engineering
      10. Tools & IDEs
      11. Web Design
      12. Web Development
      13. Web Security
      14. Programming Languages
        • PHP
        • JavaScript
      Featured

      The Intersection of Agile and Accessibility – A Series on Designing for Everyone

      July 22, 2025
      Recent

      The Intersection of Agile and Accessibility – A Series on Designing for Everyone

      July 22, 2025

      Zero Trust & Cybersecurity Mesh: Your Org’s Survival Guide

      July 22, 2025

      Execute Ping Commands and Get Back Structured Data in PHP

      July 22, 2025
    • Operating Systems
      1. Windows
      2. Linux
      3. macOS
      Featured

      A Tomb Raider composer has been jailed — His legacy overshadowed by $75k+ in loan fraud

      July 22, 2025
      Recent

      A Tomb Raider composer has been jailed — His legacy overshadowed by $75k+ in loan fraud

      July 22, 2025

      “I don’t think I changed his mind” — NVIDIA CEO comments on H20 AI GPU sales resuming in China following a meeting with President Trump

      July 22, 2025

      Galaxy Z Fold 7 review: Six years later — Samsung finally cracks the foldable code

      July 22, 2025
    • Learning Resources
      • Books
      • Cheatsheets
      • Tutorials & Guides
    Home»News & Updates»GitHub Copilot Spaces: Bring the right context to every suggestion

    GitHub Copilot Spaces: Bring the right context to every suggestion

    June 18, 2025

    When generative AI tools guess what you need, the magic only lasts as long as the guesses are right. Add an unfamiliar codebase, a security checklist your team keeps in a wiki, or a one‑off Slack thread that explains why something matters, and even the most and even the most powerful model may fill in gaps with assumptions rather than having access to your specific context and knowledge.

    GitHub Copilot Spaces fixes that problem by letting you bundle the exact context Copilot should read—code, docs, transcripts, sample queries, you name it—into a reusable “space.” Once a space is created, every Copilot chat, completion, or command is grounded in that curated knowledge, producing answers that feel like they came from your organization’s resident expert instead of a generic model. 

    In this article, we’ll walk through:

    • A 5‑minute quick‑start guide to creating your first space
    • Tips for personalizing Copilot’s tone, style, and conventions with custom instructions
    • Real‑world recipes for accessibility, data queries, and onboarding
    • Collaboration, security, and what’s next on the roadmap (spoiler: IDE integration and Issues/PR support)

    Want to learn more? Try our Docs. 

    We have everything you need to get started—including pro tips on the context that’s most helpful in your workflows.

    Explore Docs >

    Why context is the new bottleneck for AI‑assisted development

    Large language models (LLMs) thrive on patterns, but day‑to‑day engineering work is full of unpatterned edge cases, including:

    • A monorepo that mixes modern React with legacy jQuery
    • Organizational wisdom buried in Slack threads or internal wikis
    • Organization‑specific security guidelines that differ from upstream OSS docs

    Without that context, an AI assistant can only guess. But with Copilot Spaces, you choose which files, documents, or free‑text snippets matter, drop them into a space, and let Copilot use that context to answer questions or write code. As Kelly Henckel, PM for GitHub Spaces, said in our GitHub Checkout episode, “Spaces make it easy to organize and share context, so Copilot acts like a subject matter expert.” The result? Fewer wrong guesses, less copy-pasting, and code that’s commit-ready.

    What exactly is a Copilot Space?

    Think of a space as a secure, shareable container of knowledge plus behavioral instructions:

    What it holds Why it matters
    Attachments Code files, entire folders, Markdown docs, transcripts, or any plain text you add Gives Copilot the ground truth for answers
    Custom instructions Short system prompts to set tone, coding style, or reviewer expectations Lets Copilot match your house rules
    Sharing & permissions Follows the same role/visibility model you already use on GitHub No new access control lists to manage
    Live updates Files stay in sync with the branch you referenced Your space stays up to date with your codebase

    Spaces are available to anyone with a Copilot license (Free, Individual, Business, or Enterprise) while the feature is in public preview. Admins can enable it under Settings  > Copilot > Preview features.

    TL;DR: A space is like pinning your team’s collective brain to the Copilot sidebar and letting everyone query it in plain language.

    Quick-start guide: How to build your first space in 5 minutes

    1. Navigate to github.com/copilot/spaces and click Create space.
    2. Name it clearly. For example, frontend‑styleguide.
    3. Add a description so teammates know when—and when not—to use it.
    4. Attach context:
    • From repos: Pull in folders like src/components or individual files such as eslint.config.js.
    • Free‑text hack: Paste a Slack thread, video transcript, onboarding checklist, or even a JSON schema into the Text tab. Copilot treats it like any other attachment.
    1. Write custom instructions. A sentence or two is enough:
    • “Respond as a senior React reviewer. Enforce our ESLint rules and tailwind class naming conventions.”
    1. Save and test it. You’re done. Ask Copilot a question in the Space chat—e.g., “Refactor this <Button> component to match our accessibility checklist”—and watch it cite files you just attached.

    Pro tip: Keep spaces focused

    Instead of dumping your entire repo into one space, create smaller, purpose‑built spaces like: Accessibility, Data‑Queries, Auth‑Model, etc. Kelly, the PM behind the feature, uses this pattern internally at GitHub to make subject‑matter expertise reusable. 

    Personalize Copilot’s coding style (and voice, too) 

    Custom instructions are the “personality layer” of a space and where spaces shine because they live alongside the attachments. This allows you to do powerful things with a single sentence, including:

    • Enforce conventions
      •  “Always prefer Vue 3 script setup syntax and Composition API for examples.”
    • Adopt a team tone
      • “Answer concisely. Include a one‑line summary before code blocks.”
    • Teach Copilot project‑specific vocabulary
      •  “Call it ‘scenario ID’ (SCID), not test case ID.”

    During the GitHub Checkout interview, Kelly shared how she built a personal space for a nonprofit side project: She attached only the Vue front‑end folder plus instructions on her preferred conventions, and Copilot delivered commit‑ready code snippets that matched her style guide on the first try.

    Automate your workflow: three real‑world recipes

    1. Accessibility compliance assistant

    Space ingredients

    • Markdown docs on WCAG criteria and GitHub’s internal “Definition of Done”
    • Custom instruction: “When answering, cite the doc section and provide a code diff if changes are required.”

    How it helps: Instead of pinging the accessibility lead on Slack, you can use Spaces to ask questions like “What steps are needed for MAS‑C compliance on this new modal?” Copilot summarizes the relevant checkpoints, references the doc anchor, and even suggests ARIA attributes or color‑contrast fixes. GitHub’s own accessibility SME, Katherine, pinned this space in Slack so anyone filing a review gets instant, self‑service guidance.

    2. Data‑query helper for complex schemas

    Space ingredients

    • YAML schema files for 40+ event tables
    • Example KQL snippets saved as .sql files
    • Instruction: “Generate KQL only, no prose explanations unless asked.”

    How it helps: Product managers and support engineers who don’t know your database structures can ask, “Average PR review time last 7 days?” Copilot autocompletes a valid KQL query with correct joins and lets them iterate. Result: lets PMs and support self-serve without bugging data science teams.

    3. Onboarding Hub and knowledge base in one link

    Space ingredients

    • Key architecture diagrams exported as SVG text
    • ADRs and design docs from multiple repos
    • Custom instruction: “Answer like a mentor during onboarding; link to deeper docs.”

    How it helps: New hires type “How does our auth flow handle SAML?” and get a structured answer with links and diagrams, all without leaving GitHub. Because spaces stay in sync with main, updates to ADRs propagate automatically—no stale wikis.

    Collaboration that feels native to GitHub

    Spaces respect the same permission model you already use:

    • Personal spaces: visible only to you unless shared
    • Organization‑owned spaces: use repo or team permissions to gate access
    • Read‑only vs. edit‑capable: let SMEs maintain the canon while everyone else consumes

    Sharing is as simple as sending the space URL or pinning it to a repo README. Anyone with access and a Copilot license can start chatting instantly.

    What’s next for Copilot Spaces?

    We’re working to bring Copilot Spaces to more of your workflows, and are currently developing:

    • Issues and PR attachments to bring inline discussions and review notes into the same context bundle.
    • IDE Integration: Query Spaces in VS Code for tasks like writing tests to match your team’s patterns.
    • Org‑wide discoverability to help you browse spaces like you browse repos today, so new engineers can search “Payments SME” and start chatting.

    Your feedback will shape those priorities. Drop your ideas or pain points in the public discussion or, if you’re an enterprise customer, through your account team. 

    Get started today

    Head to github.com/copilot/spaces, spin up your first space, and let us know how it streamlines your workflow. Here’s how to get it fully set up on your end: 

    1. Flip the preview toggle: Settings > Copilot  >  Preview features > Enable Copilot Spaces.
    2. Create one small, high‑impact space—maybe your team’s code‑review checklist or a set of common data queries.
    3. Share the link in Slack or a README and watch the pings to subject‑matter experts drop.
    4. Iterate: prune unused attachments, refine instructions, or split a giant space into smaller ones.

    Copilot Spaces is free during the public preview and doesn’t count against your Copilot seat entitlements when you use the base model. We can’t wait to see what you build when Copilot has the right context at its fingertips.

    The post GitHub Copilot Spaces: Bring the right context to every suggestion appeared first on The GitHub Blog.

    Source: Read More 

    Facebook Twitter Reddit Email Copy Link
    Previous ArticleCyberagentschap VS meldt actief misbruik van lek in Linux-kernel
    Next Article Managing Providers in Terraform: AWS, Azure, and GCP

    Related Posts

    News & Updates

    The best CRM software with email marketing in 2025: Expert tested and reviewed

    July 22, 2025
    News & Updates

    This multi-port car charger can power 4 gadgets at once – and it’s surprisingly cheap

    July 22, 2025
    Leave A Reply Cancel Reply

    For security, use of Google's reCAPTCHA service is required which is subject to the Google Privacy Policy and Terms of Use.

    Continue Reading

    Hyprland Escluso dalla Prossima Versione di Debian 13 “Trixie”

    Linux

    DietPi – extremely lightweight Debian-based distribution

    Linux

    Flyby tracks and predicts passes of satellites in Earth orbit

    Linux

    Making Animations Smarter with Data Binding: Creating a Dynamic Gold Calculator in Rive

    News & Updates

    Highlights

    Development

    Securely Store API, Bearer and Auth Tokens with Platform Cache

    May 29, 2025

    Imagine you are retrieving an API key/Bearer token from an external system to make a…

    CVE-2025-46756 – Apache HTTP Server Unvalidated User Input

    April 29, 2025

    Ubisoft’s delay of Assassin’s Creed Shadows worked out so well, the company is pushing back some of its biggest hitters — potentially as far as March 2028

    May 15, 2025

    Cost Effective Reseller Platforms for Buying SSL Certificates

    July 16, 2025
    © DevStackTips 2025. All rights reserved.
    • Contact
    • Privacy Policy

    Type above and press Enter to search. Press Esc to cancel.