delivery-schedule

Put this repository's schedules from the catalog into the host's scheduler for the first time — its Routines page in Claude Code, its Automations page in the GitHub Copilot app — asking which to enable, creating each selected one, and stamping the selection under components.schedule in .devbook/config.json. Refused where components.schedule already exists: run delivery-schedule:update. Use when: setting up recurring unattended runs for a repository, scheduling routines or automations. Triggers on: "schedule init", "set up my routines", "set up my automations", "schedule this repository".

The unattended stack update: run devbook-config:update with the safe answer at every question it would ask a person, so outstanding migrations run and stale copies are re-materialized from the plugins the session loaded, and land the result as one draft pull request — or a schedule-report issue when only a person's step is left. The weekly devbook-update schedule's target.

The unattended devbook validation: run devbook:validate over every adopted folder, fix what it reports in the source Markdown, refresh the committed _meta/ indexes where devbook-derived keeps them, and land the result as one pull request — or a schedule-report issue when devbook-config:doctor, where installed, finds the installation needs a person. The daily devbook-validate schedule's target.

The unattended drift check: run devbook:verify-change over every adopted folder, one run per kind, and open one issue per code-ahead or conflict row nothing already covers. Reports and never writes a chapter, a brief, or a capture plan. The weekly devbook-verify schedule's target.

Tighten the instruction assets a repository loads into a model — AGENTS.md and its host twins, rules, skills, agents, prompts, contracts: cut sentences that change nothing, replace a duplicate with a pointer, turn a prohibition positive, strip hedging, fix pointers that no longer resolve. Lands as one draft pull request, one commit per file, with a ledger of every cut; skips what the previous run's rejected pull request touched.

The unattended issue sweep: classify every open issue nobody has classified yet in the repository's own labels, close the ones high-confidence evidence shows already resolved, resolve up to N of the rest one at a time — each on its own branch, each landing as a draft pull request — and publish one brief of what was labelled, closed, opened, and left for a person. Also runnable by hand; the weekday issue-sweep schedule's target. At maxResolve 0 it is the triage alone.

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.

Report what changed in this repository since yesterday and what needs a person today, in one screen: failed runs on the base branch, pull requests waiting on someone, what merged, what opened, and what the schedules landed overnight. Picks its own window, so it runs unattended each weekday morning; run it by hand to catch up after time away.

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:init or delivery-schedule:update, 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.

The unattended technology-graph refresh: run devbook:tech-update over every tech/ layer the repository has and land what moved as one draft pull request, never a merge. The weekly tech-update schedule's target.

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.

Report a repository's week as one update a stakeholder can read: what shipped, what is in flight, the issues opened and closed, releases, failed runs on the base branch, what the schedules landed, and what carries into next week — with the numbers beside the narrative. Picks its own window, so it runs unattended at the end of each week; run it by hand for any date range.

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.

Bring the host's scheduler level with this repository's schedule selection — its Routines page in Claude Code, its Automations page in the GitHub Copilot app — creating or updating each selected schedule, disabling the rest, and rewriting components.schedule in .devbook/config.json. Idempotent by name. Refused where no components.schedule stamp exists: run delivery-schedule:init. Use when: changing a cadence, adding or removing a schedule, or after upgrading this plugin. Triggers on: "schedule update", "update my routines", "update my automations", "change a cadence", "add a schedule", "remove a schedule".