AIFlare — Context for your AI-written code, solo or as a team

Overview

Weekly Team Digest consolidates the entire team's work for a week into one report. Unlike individual summaries, it aggregates contributions from all members in the project to give a team-level perspective. Run /weekly-digest in Claude Code: the MCP tool fetches the week's data, the LLM writes a Markdown report, and the result is saved on the server — it appears in the project console's Weekly Digest list immediately, without a separate publishing step.

DEV / PM Modes

The same week's data can be summarized through two lenses, chosen by the first command argument (`dev` or `pm`). When omitted, the mode defaults to DEV.

DEV

DEV mode (for engineers)

Keeps technical vocabulary intact — commit hashes, file paths, class and function names — and reports per-member work, tag distribution, and core design decisions. Designed for code reviews, team retros, and engineer 1:1s.

PM mode (for non-engineers)

Drops technical jargon entirely and re-narrates the week's work in product-facing terms ('checkout screen', 'admin page') framed around business impact. Suited for manager reports, internal weekly updates, and stakeholder syncs.

Report Structure

Section layout and vocabulary differ by mode. Every section is rendered even when data is sparse — empty sections are replaced with copy like 'limited activity this week' rather than omitted, so the structure stays consistent.

DEV

Title — One-sentence summary including the week identifier (e.g. 2026-W15)

Overview — 2–3 sentences capturing total commits, sessions, active members, and focus areas

Key Decisions — The centerpiece of the report — what was chosen, why, and what alternatives were rejected. Written as the longest, most detailed section.

Member Summary — Key contributions and sessions for each active member

Tag Distribution — Breakdown of work by tag — FEATURE / BUGFIX / REFACTORING etc.

Most Changed Files — Files that received the most edits and why they were hotspots

Continuity Notes — Work that spans multiple members or builds on previous sessions

Title — One-sentence summary including the week identifier (e.g. '2026-W15: Payment module launched and monitoring beta in progress')

Key Achievements This Week — 2–3 bullets framing this week's progress in user- and business-facing terms

Key Decisions and Their Impact — Re-narrates the week's decisions in non-technical language with a one-line business/product impact

Team Workload Distribution — How effort was distributed by member and area. If work concentrated in one area or one person, that fact is stated explicitly

Reference Statistics — Total commits, active member count, and tag breakdown in a brief appendix tone

DEV mode's Key Decisions section captures intent, alternatives, and trade-offs — it is intentionally the longest and most detailed part of the report, and is the value AIFlare adds on top of a plain git log.

PM mode deliberately omits commit hashes, file paths, class/function names, and jargon such as 'refactoring', 'migration', 'endpoint', 'query', 'schema', 'DI', 'JPA'. The LLM is also explicitly blocked from inventing facts that aren't in the data (meetings, customer feedback, schedules, etc.).

Usage Guide

Command Syntax

Type the command below in the Claude Code conversation window. Both arguments are optional — when the mode is omitted, dev is used; when the week is omitted, the current ISO week is used.

/weekly-digest [dev|pm] [week?]

Parameters

Name	Type	Required	Default	Description
audience	dev \| pm	Optional	dev	Target reader for the report — dev or pm (case-insensitive). Defaults to dev when omitted.
week	string	Optional	current week	Target ISO 8601 week in YYYY-Www format (e.g. 2026-W15). Defaults to the current week when omitted.

Argument order: audience → week. Example: /weekly-digest pm 2026-W15. When the mode is omitted, the first argument is interpreted as week.

Execution Flow

1The skill prompt loads, parses the arguments to resolve audience (dev|pm) and week, and runs git log to detect the language used in recent commit messages — the report is written in that language.

2The get_weekly_digest tool retrieves the week's per-member work, key decisions, and project statistics. The response header indicates whether you are in DEV or PM mode, and the formatter branches accordingly.

3Based on the resolved mode, the LLM generates a Markdown report that follows the 7-section DEV spec or the 5-section PM spec. The two are never mixed, and PM mode blocks technical vocabulary and invented facts.

4The report is printed verbatim in the conversation window.

5The save_weekly_digest_report tool stores the report on the server together with week, title, content, and audience. The report shows up in the project console's Weekly Digest list immediately — there is no separate publish step.

Error Reference

aiflare.yml not found

aiflare.yml is missing from the project root or api_key is empty. See the Getting Started guide to place it.

No data for week

No entries were captured for the specified week. Verify that an AI agent actually committed during that week.

Save failure

The report has already been printed in the conversation. If only the save step failed, copy the printed content for use elsewhere.