memtrace-dailylisted

Orient at the start of a coding session, review what recently changed in a repository, and self-audit after completing work. Use when the user wants the daily briefing (what changed in the last 24h with complexity deltas), hotspots (complexity × churn refactor priorities), or a session review (clean/review/risky verdicts per editing session). For catching up after time away or resuming a prior session, use memtrace-session-continuity; daily is the last-24h briefing + hotspots + self-audit. Do not reconstruct recent activity from git log; Memtrace diffs the graph at save granularity.
syncable-dev/memtrace-public · ★ 474 · AI & Automation · score 79

Install: claude install-skill syncable-dev/memtrace-public

## Overview Session bookends: orient before you start, audit before you finish. All three tools read the bi-temporal version history — every save is a change event with complexity deltas, so "what happened" includes "did it make the code better or worse". ## Quick Reference | Tool | Purpose | |------|---------| | `get_daily_briefing` | Last 24h diffed at graph level: changed functions with complexity deltas, new functions, new endpoints, per-module distribution | | `find_hotspots` | Functions ranked by complexity × recent changes — the ordered refactor priority list | | `review_agent_sessions` | Editing sessions clustered by actor, judged clean / review / risky | > **Parameter types:** MCP parameters are strictly typed. Numbers Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root). > (`window_hours`, `window_days`, `top_n`) must be JSON numbers. ## Steps ### 1. Orient at session start `get_daily_briefing` with `repo_id`. Read the summary first: - `net_cyclomatic_delta` positive → recent work added complexity; check whether your task touches the same area before piling on. - `changed` rows with large positive deltas → recently-destabilised code; prefer `preflight_check` before editing anything in that list. ### 2. When the task is refactoring or cleanup `find_hotspots` — work the list top-down. A hotspot you simplify pays off on every future change; a complex-but-untouched function can wait. ###