---
name: weekly-recap
context: fork
agent: general-purpose
description: Generates an interactive HTML recap of the user's own engineering work over one Monday-to-Friday workweek, ready for a weekly standup, 1:1 prep, or sharing with colleagues. Use when the user asks what they worked on, shipped, merged, reviewed, or moved tickets and docs on over a week ("this week", "last week", "the week of" a date), or asks for a "weekly recap", "weekly standup", "weekly summary", "week in review", or "weekly update", including phrasings like "throw together what I did last week". Not for a single day or part of a day, for a multi-day range that is not a Monday-to-Friday week or for several weeks at once (use the daily-recap skill), for looking up a single specific PR, commit, ticket, or document, for someone else's activity, for meeting recaps, for repository-level overviews, or for critiquing how a single Claude Code session went.
title: weekly-recap
canonical_url: https://skilld.dev/gh/bitwarden/ai-plugins/weekly-recap
last_updated: 2026-11-12T03:08:03.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [README.md](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/weekly-recap/README.md).
>
> If the user asked to install this Skill, run `npx skilld install bitwarden/ai-plugins/weekly-recap`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/weekly-recap`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/bitwarden/ai-plugins/weekly-recap) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/weekly-recap`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/weekly-recap --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/weekly-recap --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Weekly Recap

Generate the daily-recap page for a whole workweek. This skill defines only what differs for a week. Everything else comes from the daily-recap skill in the same plugin.

## Using the daily-recap skill

Read `${CLAUDE_PLUGIN_ROOT}/skills/daily-recap/SKILL.md` and follow its workflow (steps 1-7), its `references/render-guide.md`, and its rules on escaping, credentials, untrusted text, the Content-Security-Policy, and deleting `work/`. Where this file says something different, this file wins.

That file is read as plain text, so two things in it need translating:

- Its relative paths (`scripts/`, `assets/`, `references/`) are under `${CLAUDE_PLUGIN_ROOT}/skills/daily-recap/`. Call the scripts by that absolute path.
- Its `${CLAUDE_PLUGIN_DATA}` stays literal, because that file is read as plain text rather than loaded as a skill. Use the path substituted into this file: `out_dir="${DAILY_RECAP_OUTPUT_DIR:-${CLAUDE_PLUGIN_DATA}/daily-recaps}"`. If the result still contains `${` or begins with `/daily-recaps`, the plugin data variable was empty; stop and report that this skill must run from the installed plugin.

## The week

A week is the five workdays Monday through Friday. Each workday uses daily-recap's day boundary (`DAILY_RECAP_CUTOFF_HOUR`, default 07:00, and `TZ`), so the week runs from the cutoff on Monday to the cutoff on Saturday. Pick the dates, then take the actual bounds from the scripts' `window` output rather than recomputing them.

- "last week", "weekly standup", or no time given: the most recent Monday-to-Friday week whose Friday workday has ended.
- "this week": Monday of the current week through today. Today's window ends in the future, which is fine.
- A specific date: the Monday-to-Friday week containing it.

To step between dates, source `${CLAUDE_PLUGIN_ROOT}/skills/daily-recap/scripts/date-utils.sh` and use `add_days`, which handles GNU and BSD `date`. For a date's weekday, use `epoch_fmt "$(local_to_epoch "YYYY-MM-DD 12:00:00")" '%u'` (1=Monday) rather than `date -d`, which is GNU-only and silently returns today's weekday on BSD `date`.

## Collecting

In daily-recap's step 1, run (a), (b), and (d) once per workday in the week, passing that day's date and naming each file by it (`events-YYYY-MM-DD.json`, `sessions-YYYY-MM-DD.json`, `atlassian-YYYY-MM-DD.json`). In (b), read the window bounds from that day's `events-YYYY-MM-DD.json` rather than the `events.json` the step names. Run (c) once for the whole week: `gather-gh-search.sh MONDAY LAST-DAY`, where LAST-DAY is Friday, or for "this week" the earlier of today and that week's Friday. Skip (e) and leave `{{TODAY_BANNER}}` empty: "this week" already covers today, and for a past week the banner would sit across a weekend gap.

GitHub's events feed holds only the last 300 events from the last 30 days, so a busy week can be truncated, and a week more than 30 days old has no events at all. When any day's `feed_complete` is `false`, say so in the recap and rely on `search.json` for PRs.

Merge the per-day session digests before step 4, and the remaining per-day results before step 5. A session or PR that spans several days is one item, and a stream can run across the whole week.

## Rendering

- Page file: `recap-week-YYYY-MM-DD.html` in `$out_dir`, named by Monday's date. Use this name in steps 6 and 7.
- Page title: in the copied page, replace "Daily Recap" with "Weekly Recap" in the `<title>`, the "Engineering Daily Recap" header span, the "Daily Recap · Interactive" eyebrow, and the "Bitwarden · Engineering Daily Recap" footer. All four sit outside the `<script>` block, so the Content-Security-Policy hash is unaffected.
- `{{DATE}}`: the range, for example `2026-10-19 – 2026-10-23`.
- `{{STANDUP_PERIOD}}`: `Week · {range}`.
- `{{STANDUP_LABEL_PAST}}` is `Last week` and `{{STANDUP_LABEL_NEXT}}` is `This week`, per the render guide's Weekly column.
- Stats sum across the week. Count each PR, repository, and session once, and follow the render guide's dedupe rules for Jira and Confluence.
- Timeline: order events across the week and put a day divider before each day's events, using the After Midnight divider's markup with the text `{Weekday} · {YYYY-MM-DD}`. Each event's `tl-time` span reads `{Ddd} {HH:MM}` rather than `{HH:MM}`, so the day stays legible when the project or search filter hides the events under a divider. Leave out the After Midnight divider; post-midnight events stay under their workday.
- The BLUF and Last week bullets summarize the week's main outcomes, not each day in turn.
