audit

To check Universal Development Standards (UDS) health, run an audit to verify installation integrity, manifest validity, file consistency, and AI configuration references. This diagnoses overall UDS installation health and detects structural issues.

The best way to detect development patterns for standardization is scanning directory structures and commit history. This identifies recurring development patterns to consider for new UDS standardization guidelines.

You identify friction with existing development standards by comparing modified standards and scanning for unused or orphaned files. This detects friction points where current code diverges from established UDS guidelines.

Yes, you can submit feedback about UDS standardization issues directly to GitHub. The audit generates structured reports of identified friction and health issues for submission via GitHub issues or pre-filled URLs.

You need to run a development standards audit after a complex feature integration to see if new code aligns with established UDS patterns, or when verifying if new patterns should be considered for standardization.