Skip to content
This repository was archived by the owner on Oct 20, 2025. It is now read-only.
This repository was archived by the owner on Oct 20, 2025. It is now read-only.

[FR] Support for Multiple Custom Instruction Files #12

@ghost

Description

Problem

The Copilot Coding Agent currently limits custom instructions to a single file, typically .github/copilot-instructions.md. This contrasts with the latest updates in VS Code, which now support a .github/instructions folder to house multiple Markdown files as instructions. This inconsistency breaks the seamless developer experience across environments and limits the organization and modularity of custom instructions for the Copilot Coding Agent.

Solution

Extend the Copilot Coding Agent's custom instruction capabilities to support multiple files within a designated folder, such as .github/instructions/, aligning with the functionality introduced in VS Code. This would involve:

  • Reading Multiple Files: The agent should be able to parse and incorporate instructions from all Markdown files within the specified instructions directory.
  • Consistency with VS Code: Ensure that the implementation adheres to the .github/instructions folder structure adopted by VS Code to maintain a consistent developer experience.

Benefits

  • Improved Organization: Allows for better structuring and categorization of custom instructions, especially for large or complex projects.
  • Enhanced Modularity: Enables the creation of specialized instruction files for different aspects of a project (e.g., frontend, backend, testing, documentation), improving clarity and maintainability.
  • Consistency Across Environments: Ensures that custom instructions behave uniformly between the Copilot Coding Agent and VS Code, reducing friction for developers.
  • Easier Management: Facilitates easier updates and additions to custom instructions by allowing smaller, focused files instead of a single, monolithic file.
  • Increased Flexibility: Supports more sophisticated and granular control over the agent's behavior based on specific project requirements.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions