dld-audit-auto

To detect drift between code annotations and decision records, you can run an autonomous audit that identifies orphaned annotations, references to superseded decisions, stale file references, and unannotated code changes within your repository.

Yes, you can automatically fix unreferenced code changes and outdated decision logs by running an audit that updates annotations, corrects references, or creates new decision records, ultimately generating a Git branch with the applied fixes.

Code decision log drift occurs when code changes no longer align with their documented reasoning. Automated auditing works by scanning the repository to find discrepancies and generating a pull request summarizing detected issues and applied fixes.

You integrate decision log drift detection into your CI pipeline by running the autonomous audit during the workflow to catch and automatically correct drift between your code and its decision log before it becomes a problem.

Yes, the automated audit opens a pull request for reviewed code fixes. It generates a Git branch containing the fixes applied to annotations and references, facilitating a review of the automated changes before merging.

The primary limitation of autonomous decision log auditing is that automated fixes are not merged directly; the skill generates a Git branch and opens a pull request, requiring human review to verify the updated annotations and newly created decision records.