DEVOPS

Weekly Vercel Bundle Budget Digest to Linear

On a weekly schedule, summarizes which routes are closest to or over their bundle-size budget across recent production deploys and opens a prioritized Linear issue with the top…

CategoryDevOps
Enginesim
Difficultybeginner
Triggerschedule
Steps4
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly Monday schedule
  • ActionQuery trailing-week production size historyPostgreSQLPostgres
  • LogicRank routes by budget consumption, drop safe ones
  • OutputOpen prioritized Linear issue with offendersLinearLinear

What it does

Produces a weekly health report on bundle-size budgets. It scans the last week of production deploys, ranks the routes by how close they are to (or past) their configured byte budget, and files a single Linear issue listing the worst offenders so the team can plan trimming work in the next sprint.

When to use it

Use it when per-PR gates catch the hard failures but you also want proactive visibility into routes drifting toward their limits. Good for an end-of-week ritual that turns slow bundle creep into tracked, prioritized engineering tasks.

How it works

  1. 1A weekly schedule triggers the flow every Monday morning.
  2. 2It queries the stored size history in Postgres for all production deploys in the trailing seven days.
  3. 3It computes each route's current size as a percentage of its budget and ranks the top offenders.
  4. 4A logic step filters out routes comfortably under budget so the report stays focused.
  5. 5It opens a Linear issue titled with the week, containing a ranked table of routes, current size, budget, and headroom remaining.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect LinearIssues, projects, cycles, triage.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.