close-day

You can automate backfilling missing daily logs by synthesizing git commit history to reconstruct records for working days missed in the last 14 days. This end-of-day audit detects gaps in project-specific daily directories and generates corresponding daily logs.

An end-of-day audit ritual synthesizes daily session logs, identifies contradictions between current work and existing project rules, and analyzes cross-session repetition to promote recurring patterns into permanent knowledge base articles.

Yes, the daily log audit requires git integration and access to the project's daily and memory file structures. It relies on git commit history to perform gap analysis and patch generation for missing daily records.

You promote recurring workflow patterns into permanent knowledge by analyzing cross-session repetition across project-specific daily directories and memory files. The skill identifies these patterns and proposes new rules or knowledge articles for your knowledge base.

The best way to identify contradictions is by running an end-of-day audit that synthesizes your current daily sessions into a structured log. The audit then compares this synthesized data against your existing project rules to highlight mismatches.

No, the auto-backfill feature reconstructs missing daily logs using git history strictly for working days missed in the last 14 days. It operates within this defined window to perform gap analysis and patch generation.