skill-diagnostics

To audit AL workspaces for coding contract violations, use a static analysis process that checks your AL objects against a declared copilot-instructions.md contract and reports traceable findings with file and line citations.

Static analysis for AL extension projects detects contract drift by comparing AL objects against declared project rules, identifying missing metadata, documentation, tests, permissions, and prohibited patterns without manual code review.

Yes, you need a copilot-instructions.md file to run a compliance check. This file declares the coding contract that the AL workspace is audited against to identify missing metadata, tests, permissions, and prohibited patterns.

Yes, you can use code audits to prepare Business Central extensions for pull request reviews. The audit identifies missing metadata, documentation, tests, permissions, and prohibited patterns before the code is merged or released.

The best way to structure compliance reports for AL object analysis is to organize issues by class and severity with file and line citations, ensuring traceable findings while avoiding unsupported assumptions about the codebase.

Contract drift occurs when AL workspace objects no longer align with the declared coding contract. Diagnose it by applying rule-based static analysis to classify violations by severity and generate file-level remediation reporting.