copilot-config

Copilot Skill

When to use

Use this skill when:

• Editing .github/copilot-instructions.md to improve Copilot behavior
• Dealing with Copilot PR review comments (via /fix-pr-comments)
• Analyzing Copilot's review patterns to identify recurring false positives
• Tuning Copilot's code suggestions for the project

Do NOT use when:

• Augment-specific behavior (use Augment rules and skills)
• Writing application code

Procedure: Configure Copilot

1. Inspect current Copilot config — Read .github/copilot-instructions.md (if any) and the What Copilot Can and Cannot Read table below to confirm Copilot Code Review vs. Chat scope.
2. Decide self-contained scope — Identify which rules must live in copilot-instructions.md (PR-review-relevant) vs. .augment/ (agent-only).
3. Apply changes — Edit copilot-instructions.md with coding-standards, review-comment rules, and any new conventions; keep it self-contained.
4. Verify — Open a draft PR, confirm Copilot reads the new rules; for Chat, ask Copilot to summarize the active instructions.

Configuration File

.github/copilot-instructions.md — the single source of truth for Copilot behavior.

What Copilot Can and Cannot Read

Key implication: copilot-instructions.md must be self-contained for PR reviews. It cannot reference .augment/ files and expect Copilot Code Review to follow them. For Copilot Chat users, a hint at the top of the file points to .augment/ for deeper context.

What Copilot Controls

Relationship to .augment/

copilot-instructions.md and .augment/ serve different audiences:

When updating coding rules, check if both files need the change:

• Architecture/coding rules → update both (Copilot needs them self-contained)
• Agent workflows/commands → only .augment/ (Copilot doesn't use these)
• PR review behavior → only copilot-instructions.md (Augment uses /fix-pr-* commands)

PR Review Comment Rules

Copilot is configured with strict comment behavior rules:

Deduplication

Before creating a comment, Copilot must:

1. Check if it already commented on the same line/concern
2. Check if another reviewer already raised the same point
3. Skip if a duplicate would be created

Reply Handling

Key Principle

One comment per concern per location. Never duplicate, never re-raise rejected suggestions.

Handling Copilot Bot Comments (as Augment Agent)

When the user asks to fix Copilot's PR review comments (via /fix-pr-comments):

1. Evaluate Each Comment

For each Copilot comment, determine:

2. Reply Format

When replying to Copilot comments on behalf of the user:

{English explanation}

---

🇩🇪 {German translation}

3. Common False Positives

Copilot frequently suggests things that conflict with project conventions:

Improving Copilot Instructions

When updating .github/copilot-instructions.md:

Structure

• Each section starts with ## ✅ {Title}
• Rules are bullet points, concise and actionable
• Code examples use ✅ Correct / ❌ Wrong pattern
• Keep sections focused — one concern per section

When to Add New Rules

When NOT to Add Rules

• Don't add rules for things ECS/Rector auto-fix (Copilot doesn't need to know)
• Don't add rules that duplicate AGENTS.md content (Copilot doesn't read AGENTS.md)
• Don't add overly specific rules for one-off situations

Relationship to Other Tools

Copilot and Augment complement each other:

• Copilot handles real-time suggestions and automated PR reviews
• Augment handles complex workflows, deep analysis, and multi-step tasks

Related

• File: .github/copilot-instructions.md — Copilot configuration
• Command: /fix-pr-comments — fix all review comments (bot + human)
• Skill: code-review — PR review process and conventions

Output format

1. Updated copilot-instructions.md or related config file
2. Summary of changes and which Copilot behavior is affected

Gotcha

• copilot-instructions.md is for GitHub Copilot, NOT for Augment — don't mix audiences.
• Don't duplicate .augment/ content into copilot-instructions.md — it bloats the file and causes drift.
• Copilot reads the ENTIRE instructions file on every request — keep it under 500 lines.

Do NOT

• Do NOT let Copilot generate code that violates project coding standards.
• Do NOT accept Copilot review comments without verifying them against the codebase.

Auto-trigger keywords

• GitHub Copilot
• copilot instructions
• PR review
• copilot behavior