minutes-lint

You identify decision conflicts across multiple meetings by running a cross-meeting consistency check that surfaces contradictions and stale commitments. The audit produces a JSON report for machine processing and a Markdown summary for human review.

Auditing stale commitments in meeting history involves running a consistency check with the optional --stale-after-days filter. This surfaces overdue actions and outputs a structured JSON report alongside a readable Markdown summary.

You can filter meeting audits to show commitments for a specific owner by applying the optional --owner parameter. This focuses the consistency check on individual responsibilities before generating the JSON and Markdown reports.

The meeting lint output supports machine processing by generating a structured JSON report. It also formats results into readable Markdown, including frontmatter-driven resolution status when available for human review.

Checking for decision contradictions in meeting notes is needed when auditing decision history across multiple meetings to maintain consistency. This resolves potential contradictions and tracks overdue actions before they impact project alignment.