convention-audit

You can detect convention drift by analyzing time-windowed git commits, extracting coding patterns from changed files, and comparing them against existing frontend and backend convention baselines to classify deviations.

Comparing recent code changes against frontend and backend conventions involves running a convention audit that extracts evidence via git log queries and categorizes findings into deviations, new pattern candidates, and modification candidates.

Yes, you can filter convention audit results by specific team members. The analysis supports time-windowed and optional team-member-filtered reviews for both frontend JavaScript and backend Java or SQL code changes.

You can safely update convention documents by selecting approved items from the audit report and applying them to convention files without deleting prior content, ensuring changes are tracked with explicit tags and changelog updates.

Yes, convention audit works with both Java and JavaScript codebases. It analyzes backend code changes in Java and SQL alongside frontend JavaScript changes to detect convention drift against existing baselines.

Automated convention drift detection requires existing convention baselines and relies on frequency thresholds to categorize findings. It only applies approved items back into convention files, meaning unapproved patterns remain unupdated.