chat-recall-projectlisted

Get the state of a project from chat-recall. Use when the user asks "what's been happening in <project>", "catch me up on this repo", "what's the state of X", about time/cost/activity across a project, or about code findings and recommended fixes. Owns the ranked findings views — "what should I fix next", "what should I work on", "what should I tell Claude about this repo", "turn these findings into tasks". Also owns the shared task board and the team view — "what are my open tasks", "create a task for…", "what is my team working on", "which projects are shared". Aggregates sessions, plans, tasks, commits, cost, knowledge graph, and code-intelligence for one project.
munhq/chat-recall · ★ 2 · AI & Automation · score 65

Install: claude install-skill munhq/chat-recall

# Project intelligence with chat-recall ## The one-call overview `recall_project_context` — the full project dossier: overview, tech stack, decisions log, recent sessions with summaries, open tasks, plans, diary conclusions, and cost. Accepts a path, a name substring, or a project id (`git:host/owner/repo`, `git-local:<sha1>` for a repo with no remote, `ws:name`, `user:custom`). Start here for "catch me up on this project". ## Activity, cost, trends - `recall_weekly_digest` — sessions, cost, top projects, trend vs last week, open tasks, git activity. `weeks_back: 0` = this week. - `recall_analytics_summary` — cross-tool spend & activity totals (sessions, cost, top tools/projects/models). This one is NOT project-scoped, so it is the right call for "how much did I spend this month" across everything. - `recall_outcome_summary` — how sessions ended over the last N days (shipped / interrupted / abandoned), for "am I finishing what I start". ## Code intelligence (when the codeindex companion is present) - `recall_code_projects` — indexed projects with health score. - `recall_code_findings` — findings (security / clones / dead code / coupling / cycles …); each carries a ready-to-run agent prompt. Filter by `project`, `severity`, `category`. - `recall_code_actions` — the ranked "what to fix next" plan. - `recall_recommendations` — concrete recommendations (`scope: 'project'` with a `project` id) reasoning over code + how sessions went. - If a repo isn't indexed