dld-audit-auto

Audit code annotations against decision records and open a pull request with fixes.

4|Updated Mar 7, 2026

Search Tags:#automation #code review #drift detection #audit #decision log #ci #dld

Ready to run

npx skills add https://github.com/jimutt/dld-kit --skill dld-audit-auto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dld-audit-auto
Source: https://github.com/jimutt/dld-kit/tree/main/.claude/skills/dld-audit-auto
Command: npx skills add https://github.com/jimutt/dld-kit --skill dld-audit-auto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automatically detects and fixes discrepancies between your codebase and its associated decision logs, ensuring that code changes align with their documented reasoning.

Core Features & Use Cases

Drift Detection: Identifies issues like orphaned annotations, references to outdated decisions, and unannotated code changes.
Automated Fixing: Attempts to resolve detected issues by updating annotations, references, or even creating new decision records.
PR Generation: Creates a pull request summarizing all detected issues and the fixes applied, facilitating a review of automated changes.
Use Case: Run this skill in your CI pipeline to catch and automatically correct drift between your code and its decision log before it becomes a problem.

Quick Start

Run the autonomous audit to detect and fix drift, then create a pull request.

Frequently Asked Questions about dld-audit-auto

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

FAQPage Schema

How do I detect drift between code annotations and decision records?▼

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.

Can I automatically fix unreferenced code changes and outdated decision logs?▼

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.

What is code decision log drift and how does automated auditing work?▼

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.

How do I integrate decision log drift detection into my CI pipeline?▼

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.

Does the automated audit open a pull request for reviewed code fixes?▼

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.

What are the limitations of autonomous decision log auditing?▼

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.