Skip to content

feat: export_timeline tool for markdown session reports - #86

Closed
TerminalGravity wants to merge 2 commits into
mainfrom
feat/export-timeline-v2
Closed

feat: export_timeline tool for markdown session reports#86
TerminalGravity wants to merge 2 commits into
mainfrom
feat/export-timeline-v2

Conversation

@TerminalGravity

Copy link
Copy Markdown
Collaborator

Closes #5

Adds export_timeline tool (tool #25) that generates structured markdown reports from timeline data.

Formats:

  • summary — weekly aggregates with correction rates (default)
  • daily — day-by-day event breakdown with timestamps
  • full — both weekly + daily detail

Features:

  • Overall stats table (prompts, commits, corrections, tool calls, errors)
  • Weekly breakdown with correction rate tracking
  • Prompt quality trend table across days
  • Relative date support (7days, 2weeks, etc.)
  • Author filtering for commits
  • Multi-project scope support (current/related/all)

Useful for weekly reviews, standups, retrospectives, or sharing progress with teammates.

Covers common issues: LanceDB native modules, first-run model download,
missing session data, .preflight/ config not loading, tools not appearing
in Claude Code, and permission errors.
Implements #5 — adds export_timeline tool that generates structured
markdown reports from timeline data with summary/daily/full formats,
prompt quality trends, and weekly aggregates.

@TerminalGravity TerminalGravity left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great addition for standups and retros. Code looks solid.

Suggestions:

  1. Input normalizationRELATIVE_DATE_RE works for 2weeks but someone might pass 2 Weeks. Lowercase + trim before matching.
  2. Output sizefull format on a busy project could be huge. Consider an optional maxDays param or a note about reasonable ranges.
  3. This also closes #5 — might want to reference in the PR body.

Ready to ship.

@TerminalGravity TerminalGravity left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Solid feature — the three export formats (summary, detailed, full) cover good use cases. 371 lines of additions with tests, closes #5. CI green. Looks good to merge.

@TerminalGravity

Copy link
Copy Markdown
Collaborator Author

Superseded by #108.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Export timeline to markdown/PDF reports

1 participant