diagnose-months

What problem does it solve?

Diagnoses foreign key resolution failures and month-level data gaps in staged financial records to quickly identify why audit accuracy falls below 100%. It helps teams find orphaned account codes, unresolved program IDs, missing client mappings, and months with unexpectedly low or zero staging rows so they can remediate ETL and mapping issues.

Core Features & Use Cases

• Scan one or multiple YYYY-MM months in the staging table and count rows per month to detect gaps and zero-data months.
• Attempt FK resolution by joining account_code to dim_account, master_program_id to dim_master_program, and client_id to dim_client and summarize unresolved rows by type and month.
• Provide verbose output to list individual failing rows for debugging and integration with activity logging for audit trails.
• Use case: run after an audit-financials check reports accuracy below 100% to identify exactly which rows and months failed resolution.

Quick Start

Diagnose FK resolution failures and data gaps for months 2026-01 and 2025-12 and show individual failing rows by running the diagnose-months skill with months 2026-01,2025-12 and verbose enabled.