github-copilot-repo-instructions

Standardize repository-scoped GitHub Copilot instructions with applyTo frontmatter.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/paulnsorensen/skillz-that-grillz --skill github-copilot-repo-instructions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-copilot-repo-instructions
Source: https://github.com/paulnsorensen/skillz-that-grillz/tree/main/skills/github-copilot-repo-instructions
Command: npx skills add https://github.com/paulnsorensen/skillz-that-grillz --skill github-copilot-repo-instructions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams add and maintain consistent, repository-scoped GitHub Copilot guidance so Copilot Chat, Copilot code review, and the Copilot coding agent follow the same project conventions.

Core Features & Use Cases

  • Create repo-wide instruction coverage: Add guidance in .github/copilot-instructions.md to shape Copilot responses across the repository while staying under GitHub’s documented expectations (like keeping it short).
  • Add path-specific rules with globs: Use .github/instructions/<name>.instructions.md files with required applyTo frontmatter so different parts of the codebase get tailored instructions.
  • Audit and configure Copilot code review behavior: Verify and troubleshoot whether PR reviews are using the custom instruction content, including the base-branch behavior and common “Copilot is ignoring us” scenarios.

Quick Start

Add .github/copilot-instructions.md in your repository’s .github/ directory, then commit it on the base branch so Copilot code review and Chat can read it.

Frequently Asked Questions about github-copilot-repo-instructions

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

FAQPage Schema
How do I add custom instructions for GitHub Copilot in my repository?

You can configure path-specific GitHub Copilot instructions by creating `.github/instructions/<name>.instructions.md` files with mandatory `applyTo` frontmatter, allowing different codebase sections to receive tailored guidance.

Why is GitHub Copilot code review ignoring my custom instructions?

GitHub Copilot code review ignores custom instructions when the `.github/copilot-instructions.md` file is not committed on the base branch, or if path-specific files lack the required `applyTo` frontmatter for proper discovery.

What is the best way to standardize Copilot guidance across a codebase?

The best way to standardize Copilot guidance is combining a repo-wide `.github/copilot-instructions.md` file with path-specific `.instructions.md` files, ensuring consistent conventions for Chat and code review while adhering to size limits.

Can I apply GitHub Copilot instructions to specific file paths?

Yes, you can apply GitHub Copilot instructions to specific file paths by creating instruction files in `.github/instructions/` and defining glob patterns in the mandatory `applyTo` frontmatter for targeted rule delivery.

Does GitHub Copilot support path-specific rules for PR review and coding agent?

Yes, GitHub Copilot supports path-specific rules for PR review and the coding agent by merging repo-wide instructions with path-scoped `.instructions.md` files based on their `applyTo` frontmatter precedence.