policydb-config-audit

Name: policydb-config-audit
Availability: InStock
Author: wanderinglantern

Audit PolicyDB configuration coverage gaps between _DEFAULTS and EDITABLE_LISTS.

Updated Mar 23, 2026

Search Tags:#audit #config #defaults #policydb #editable_lists #deep_merge

Ready to run

npx skills add https://github.com/wanderinglantern/policydb --skill policydb-config-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: policydb-config-audit
Source: https://github.com/wanderinglantern/policydb/tree/main/.claude/skills/policydb-config-audit
Command: npx skills add https://github.com/wanderinglantern/policydb --skill policydb-config-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

Config system audit checklist for PolicyDB — _DEFAULTS ↔ EDITABLE_LISTS cross-check, deep merge limitations, and known gaps. Use when adding new config keys, modifying settings.py, or auditing config coverage.

Frequently Asked Questions about policydb-config-audit

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

FAQPage Schema

How do I audit PolicyDB config coverage gaps between defaults and editable lists?▼

Audit PolicyDB config coverage by cross-checking _DEFAULTS against EDITABLE_LISTS to identify missing keys, document deep_merge behavior, and report known configuration gaps.

What happens to new config keys during a deep_merge in PolicyDB settings?▼

Deep_merge behavior in PolicyDB settings merges nested dictionaries recursively, and auditing it documents limitations where new config keys might not integrate properly with editable lists.

When should I run a configuration coverage audit on settings.py?▼

Run a configuration coverage audit on settings.py when adding new config keys, modifying existing settings, or ensuring _DEFAULTS and EDITABLE_LISTS stay synchronized across PolicyDB.

What are the known limitations of PolicyDB editable lists for config hardening?▼

Known limitations of PolicyDB editable lists include deep_merge constraints where nested structures may not fully propagate, leaving coverage gaps between _DEFAULTS and editable configurations.

Can I check if my PolicyDB _DEFAULTS align with EDITABLE_LISTS after adding settings?▼

Yes, you can cross-check _DEFAULTS against EDITABLE_LISTS after adding settings to verify alignment, catch missing entries, and document any deep_merge coverage gaps in PolicyDB.

Why does my PolicyDB config audit show mismatches between defaults and editable fields?▼

Config audit mismatches occur when _DEFAULTS keys lack corresponding EDITABLE_LISTS entries, or deep_merge limitations prevent nested settings from properly merging into the editable configuration.