schedule-weekly-update

Generates a weekly repository update summarizing shipped work, open items, issues, releases, and failed runs.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/JSdotNet/devbook --skill schedule-weekly-update-jsdotnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: schedule-weekly-update
Source: https://github.com/JSdotNet/devbook/tree/main/plugins/delivery-schedule/skills/schedule-weekly-update
Command: npx skills add https://github.com/JSdotNet/devbook --skill schedule-weekly-update-jsdotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Stakeholders who were not in the day-to-day work need a readable account of where a repository stands each week, but compiling commits, pull requests, issues, releases, and failed runs by hand is repetitive and easy to skip. ## Core Features & Use Cases - Weekly Repository Report: Produces one update per week covering what shipped, what is in flight, issues opened and closed, releases, failed runs on the base branch, and carry-over items. - Self-Selecting Window: Picks its own date window so it can run unattended at the end of each week, or accepts an explicit ISO range for any past period. - Numbers Beside Narrative: Opens with three sentences of prose, then a metrics table, then attention-ordered sections with every item linked. - Use Case: A team lead schedules this to run every Friday so stakeholders receive a consistent weekly account of repository activity without anyone writing it manually. ## Quick Start Run the weekly update for this repository covering the last seven days and render it in chat.

Frequently Asked Questions about schedule-weekly-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a weekly repository status report automatically?▼

Run schedule-weekly-update with no arguments and it picks its own seven-day window in UTC, gathering commits, pull requests, issues, releases, and failed runs. It renders one update with prose, a numbers table, and linked sections.

How to report on a custom date range instead of the last week?▼

Pass an explicit ISO range in the form YYYY-MM-DD:YYYY-MM-DD as the window input. The run is read-only and idempotent, so re-running with the same range rewrites that past week.

Can the weekly update run unattended on a schedule?▼

Yes, it is designed to run unattended at the end of each week because it selects its own window. It is part of the delivery-schedule plugin, which syncs triggers into the host's scheduler.

What data sources does a weekly repository report include?▼

It reads commits on the base branch, merged and open pull requests, opened and closed issues, releases, and failed runs on the base branch, as defined in the change window contract. Each item appears linked in the output.

What happens when nothing changed in the reporting window?▼

An empty window produces the line 'Nothing changed since <since>.' under the numbers table, with no padded sections. Optional named sections are dropped without a heading when they return no items.