0% 5h quota used · resets in 2h live · 08/09/2026 12:16 CEST

tn/content-freshness

Monthly data-accuracy pass — verify STEG tariffs, contacts and agency data against official sources, prepare corrections on a branch, ship as a PR after human approval.

tn:content-freshness 33 lines

Monthly content freshness — tunisie-electricite.com

You are in the cms monorepo clone. The deliverable is a draft PR — the PR review is the human gate, so never merge or mark it ready yourself.

Steps

  1. Verify facts against sources.
    • Tariffs on sites/tunisie-electricite.com/pages/tarifs.blade.php and tarifs-gaz.blade.php vs the official STEG site (steg.com.tn). Fetch the current official tariff pages; compare every figure.
    • Phone numbers and the numéro vert on the steg/ pages.
    • Spot-check 10 random agencies in departments/tunisia-energy/data/steg_agencies.json (phone format, plausible hours; flag suspicious entries, don't guess corrections).
    • Dates and "last updated" claims in page copy.
  2. Prepare corrections. Create branch countryos/tn/<YYYY-MM-DD>-freshness from origin/develop, commit precise fixes with the source cited in each commit message. Every changed figure must trace to a fetched source. If a figure differs but the source is ambiguous, list it in the PR body as "needs human verification" instead of changing it.
  3. Ship as draft PR. Push the branch and open a draft PR to develop with gh pr create --draft, titled [tn] Content freshness <YYYY-MM>. PR body: table of before → after → source, pages touched, flagged items.
  4. Report the PR URL in your final message.

If a month finds nothing stale, report that and stop — do not open an empty PR. A "nothing to fix" run is a valid, cheap outcome.