delivery-schedule

Put this repository's schedules from the catalog into the host's scheduler — its Routines page in Claude Code, its Automations page in the GitHub Copilot app — creating or updating each selected one, disabling the rest, and recording the selection under components.schedule in .devbook/config.json. Idempotent by name. Use when: setting up recurring unattended runs for a repository, scheduling routines or automations, changing a cadence, adding or removing one, or after upgrading this plugin. Triggers on: "schedule install", "schedule-install", "set up my routines", "set up my automations".

Pick the single highest-priority open GitHub issue labelled 'bug', claim it, and resolve it in this session by running flow-bug through to Personal Validation. One issue per run, no extra sessions.

Review every open pull request that is waiting on a reviewer: run the code review checklist over its diff, read its checks and its distance from the base branch, and post one review comment per pull request with the findings and a merge verdict. Never approves, never merges, never pushes. Idempotent per head commit, so a daily run re-reviews only what changed.

Update all outdated NuGet packages in a .NET solution, check installed plugins for newer versions, and open a PR with the changes. Handles Central Package Management, Aspire integration upgrades, and post-update build and test verification.

Identify 10 performance improvements across the codebase, score each by impact and effort, then implement and open a PR for the single highest-impact, lowest-effort finding.

Run a full automated review cycle on the codebase or a specific scope: collects TODO items, surfaces future-improvement suggestions, and runs a structured code review. Produces a prioritised findings report and optionally opens GitHub issues for the highest-priority items.

Fire one of this repository's schedules now, outside its cadence, and report the run. Use when: running a routine or automation now, testing one right after delivery-schedule:install, or re-running one that failed.

Run a layered security review of the repository: vulnerable dependencies from the package managers' own audits, secrets committed to the tree, CI workflow hardening, and the security items of the code review checklist. Produces a severity-ranked report and opens one GitHub issue per new high-severity finding, deduplicated against the issues already open.

Show this repository's schedules and how their recent runs went — cadence, enabled state, the last runs, what each published, and the log of a run that failed or parked. Use when: checking whether a scheduled run fired, why one failed, what a routine or automation produced last night, or listing what is scheduled for this repository.

Scan configured topics for updates published in the last 7 days and produce a concise "What's new this week" digest. Default topics: .NET Aspire, Claude Code, and the Anthropic engineering blog.

Analyse the token usage the delivery-surface-dashboard recorded for the week's flow runs, surface the top actionable cost-reduction tips, and produce a concise report.

Check one or more GitHub repositories for what changed since the last run: open pull requests and pull requests merged since the last checkpoint. Correlates each PR with related Jira tickets or GitHub issues where discoverable, and persists a per-repo checkpoint so the next run only reports genuinely new activity.