A guide from GitHub shows how to adapt GitHub Copilot to project rules
GitHub describes how to provide GitHub Copilot with project rules: store shared instructions in the repository, define rules for specific files using applyTo, and describe recurring workflows or specialized tasks using agent skills and custom agents.
GitHub has published a guide to adapting GitHub Copilot to project rules. The .github/copilot-instructions.md file holds instructions that apply throughout the repository, such as architecture, naming conventions or testing requirements. Files in .github/instructions use the applyTo field to specify which files particular rules apply to. According to GitHub, the tool can combine shared and specific instructions as it works.
For recurring workflows, the guide recommends agent skills. Each set has its own subfolder in .github/skills and can contain instructions, scripts and other supporting materials. The SKILL.md file describes the workflow and helps determine when to use it. One example is .github/skills/quality-checks, which contains the project workflow for testing and static code checks using linting.
For broader tasks, such as checking accessibility across components, templates and styles, the guide describes custom agents. Their profiles in .github/agents can define their purpose, instructions, tools and relevant project context. GitHub recommends starting with one frequently repeated rule in .github/copilot-instructions.md and checking its use during the next task.
Why it matters
The guide distinguishes between persistent project rules, individual workflows and specialized roles. This helps developers choose where to store a particular requirement. According to GitHub, the tool can load this context as needed, reducing the need to explain the same conventions and commands repeatedly.
Two audiences, two different impacts
What this means
For individuals
A developer can store a frequently repeated convention directly in the repository and observe whether GitHub Copilot uses it during the next task.
For a business
The team can document its established testing and quality assurance workflow as agent skills and use custom agents to define a specialized role for recurring checks across files.
DevelopmentCheck the original
Event sources
only one source so far · 1 publisher, 0 independent. We count feeds from the same owner only once.