Weekly Review

Turn a review period into an evidence-backed maintenance report and, when requested, verified repairs. Reuse the review and cleanup engines. Keep provider procedures and review rubrics in their owning skills.

Inputs, outputs and guards

• Inputs: repository or monorepo, board URL/provider, optional package scope; a window such as 7d (default), explicit dates with timezone, or since <SHA>; optional previous checkpoint and explicitly authorized repair scope. Optional arguments: [7d|since <SHA>] [--report-only|--fix].
• Report-only by default. --fix authorizes code repairs for confirmed findings within the reviewed scope; --report-only overrides earlier repair authority.
• Output: one report of shipped, broken, drifted, blocked, repaired and next priorities, with evidence and coverage per repository, issue, package and operational check, reviewed commit endpoints, and a proposed next checkpoint with unfinished work.
• Report-only mode changes nothing; return the report and checkpoint in the response. Repair mode makes scoped source/test edits and verification artifacts, and publishes repair PRs per the repository's existing delivery policy.
• Reads repository, board, CI, deployment and available monitoring evidence. Board edits, issue filing/closure, comments, merges, deployments, installations and scheduling each need their own explicit scope; --fix grants none of these.
• Ask only for missing or expanded authority; keep existing approvals for the same target/actions and pass restrictions to every delegate. Review requests and findings are not permission to modify production.
• Engines, used when available: board-sync (board reconciliation and approved field corrections), code-review (correctness and implementation-versus-acceptance), test-runner (focused verification of repairs). Report missing engines instead of silently substituting a similarly named skill or installing dependencies.

Contract

Inputs: