review-timeline

To find gaps in your case study documentation, analyze local event logs and git history to identify missing reflections, screenshots, and commit metadata. This process compares captured content against portfolio rubrics to highlight weak coverage.

A case study events.json file records local project events like git commits, reflections, and screenshots. Parsing this file allows you to count and categorize events to assess documentation completeness against portfolio and marketing rubrics.

Check git history coverage for a portfolio by comparing commit metadata and captured reflections against a portfolio rubric. This validates that constraints, tradeoffs, risks, security, architecture, and iteration are documented.

Yes, you can generate a checklist of missing screenshots and reflections from your local project folder. Analyzing git log metadata and event logs produces a prioritized status report of required media assets and documentation.

Yes, you need a local git repository and a .case-study/events.json file to review case study status. The analysis requires access to recent git history to count commits and categorize reflections accurately.

The best way to identify missing security or architecture reflections is to compare captured events against a portfolio rubric. This generates actionable recommendations, such as adding a security reflection tied to a specific commit.