instructions-audit

To audit copilot instructions for drift, cross-reference the repository against documented guidance by reading .github/copilot-instructions.md and verifying paths, stack versions, and project structure to surface inconsistencies and generate a remediation report.

Copilot instructions drift occurs when documented guidance in copilot-instructions.md becomes outdated after refactors or convention changes. Drift detection works by cross-referencing the live codebase against the instructions to surface stale references and mismatches.

Conformance checks validate referenced paths, stack versions, and project structure against the live codebase. The audit reads .github/copilot-instructions.md and cross-references the repository to verify that documented guidance matches actual implementation.

The best way to generate a remediation report for copilot instructions is to run a full audit against your repository. This cross-references the codebase to detect drift and produces concise, actionable fixes for stale references and mismatches.

You need a .github/copilot-instructions.md file present in your repository to audit copilot instructions. The audit verifies your actual project structure, stack versions, and conventions against this documented guidance to detect drift.

Yes, you can use a gap-analysis audit during codebase refactors to maintain instruction hygiene. The audit detects drift and stale references caused by new files and changed conventions, providing remediation guidance to keep instructions aligned.