Save the operator-approved 2026-06-02 spec as example-spec.json (gold standard for voice/structure/specificity). Skill now tells the agent to match it, with one deliberate change: keep the editorial lead TIGHT (~2 short paragraphs, ~120 words). The live 2026-06-02 page stays as the reference. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
65 lines
4.7 KiB
Markdown
65 lines
4.7 KiB
Markdown
---
|
|
name: recipe-report
|
|
description: Generate the weekly public "Recipe Report" after the cc-ci /upgrade-all run. Reviews how the upgrade went and the state of every recipe + open PR, classifies what needs attention vs routine, and publishes a self-contained HTML page to report.ci.commoninternet.net (one page per week + a home index). Read-only — reports, never merges or edits PRs. Runs as its own agent (model configured separately from the upgrader; default opus). Invoke as /recipe-report [YYYY-MM-DD].
|
|
---
|
|
|
|
# recipe-report
|
|
|
|
Produce the weekly **"The Recipe Report"** — a public HTML page reviewing the latest `/upgrade-all` run
|
|
and the live state of every recipe + open PR. Served at **https://report.ci.commoninternet.net** (one
|
|
`week-<date>.html` per run + a home-page index). You are **read-only**: you report, you never merge,
|
|
edit, or comment on PRs. The page is **public + unauthenticated** — include only public-safe data
|
|
(recipe names, version bumps, PR titles/links, CI verdicts, concise error summaries); **never** secrets,
|
|
tokens, internal IPs, or raw logs.
|
|
|
|
Helper: `python3 /srv/cc-ci/cc-ci-plan/recipe-report.py {survey|render|publish}` (see its header).
|
|
|
|
## Procedure
|
|
|
|
1. **Pick the date.** `DATE` = the argument, else today (UTC). The `/upgrade-all` summary for that run is
|
|
`/srv/cc-ci/.cc-ci-logs/upgrades/upgrade-all-<DATE>.md`.
|
|
|
|
2. **Survey.** `python3 /srv/cc-ci/cc-ci-plan/recipe-report.py survey <DATE> > /tmp/survey.json`. This
|
|
gives you: the raw `/upgrade-all` summary; for every recipe mirror its open PRs + the `cc-ci/testme`
|
|
verdict; and each recipe's **per-recipe upgrade notes** (`upgrade_notes_md` — the breaking-change /
|
|
**CVE / security** analysis the upgrade did). Read it all.
|
|
|
|
3. **Review & classify — this is a front page, write it like an editor.**
|
|
- **Security first.** Scan the per-recipe `upgrade_notes_md` + the summary (and use your own knowledge
|
|
of the version bumps) for upgrades that fix **CVEs / security issues**. Anything **critical/high**
|
|
leads the page → the `security` bulletin (recipe · CVE id(s) + severity · what it fixes · PR link).
|
|
This is the most important section; be specific about severity and what's exposed if not merged.
|
|
- **Lead / editorial.** Write the `lead`: the **overall state of the recipe fleet** this week (how
|
|
healthy, what moved, any worrying trend) and **specific, opinionated suggestions of what to focus
|
|
on** — opus's voice, useful and concrete. **Keep it TIGHT: 2 short paragraphs, ~120 words total** —
|
|
lead with the single most important thing, then security/focus in a sentence or two. (Trim hard;
|
|
the rest of the page carries the detail.)
|
|
- **Needs attention** — GREEN PRs ready to merge + errors/failures to investigate (RED `!testme`,
|
|
recipe bugs). Short, specific prose + links. Flag cross-cutting issues (e.g. two open PRs to reconcile).
|
|
- **Routine** — minor/clean bumps, stale-test PRs (need operator `--with-tests`), up-to-date / skipped.
|
|
|
|
4. **Write the spec** `/tmp/report-spec.json` (shape in the helper header): `date`, `subtitle`
|
|
("Week of <human date>"), `lead` (the editorial, blank-line-separated paragraphs), `security[]`
|
|
(critical-CVE upgrades — may be empty), `needs_attention[]`, `routine[]`, and a **comprehensive
|
|
`table[]`** with EVERY recipe (`recipe`, `change` "a → b", `status`
|
|
GREEN/STALE/FAILED/SKIPPED/UPTODATE, `ci` as a level/result number+info string e.g. `build 154 ✓`
|
|
or `RED · restore` with `ci_url`, `pr`/`pr_url`, `notes`). **CI = link + number/info only; no images.**
|
|
|
|
**Template — match this.** `.claude/skills/recipe-report/example-spec.json` is the gold-standard
|
|
example (the 2026-06-02 report; the operator approved its style/format). **Match its editorial voice,
|
|
structure, field shapes, and level of specificity** — the only deliberate change is the **shorter
|
|
`lead`** described above. Read it before writing your spec.
|
|
|
|
5. **Render & publish.**
|
|
`python3 .../recipe-report.py render /tmp/report-spec.json /tmp/week-<DATE>.html`
|
|
`python3 .../recipe-report.py publish /tmp/week-<DATE>.html <DATE>`
|
|
(publish copies the page to `cc-ci:/var/lib/cc-ci-reports/` and regenerates the index.)
|
|
|
|
6. **Verify & stop.** `curl -fsS https://report.ci.commoninternet.net/week-<DATE>.html` renders and the
|
|
index lists it. Print the report URL and `RECIPE REPORT COMPLETE`, then go idle (one-shot — do not loop).
|
|
|
|
## Guardrails
|
|
- **Read-only.** Never merge/edit/comment on PRs or touch recipes/tests. You only describe + link.
|
|
- **Public-safe.** No secrets/tokens/internal hostnames/raw logs on the page. Summarize errors.
|
|
- One page per run; always regenerate the index so all weeks are listed (newest first).
|