SkillsAdd

getsentry/sentry-javascript · Archived

bump-size-limit

Bump size limits in .size-limit.js when the size-limit CI check is failing.

First seen Mar 20, 2026

Installation

$ npx skills add getsentry/sentry-javascript --skill bump-size-limit
View on skills.sh ↗ GitHub repository ↗

Summary

  • Bump size limits in .size-limit.js when the size-limit CI check is failing.
  • Use when the user mentions size limit failures, bundle size checks failing, CI size check errors, or needs to update size-limit thresholds.
  • Also use when the user says "bumpSizeLimit", "fix size limit", "size check failing", or "update bundle size limits".

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

fix-security-vulnerability Same source · more installs
getsentry/sentry-javascript

Analyze and propose fixes for Dependabot security alerts

20 installs
skill-creator Same source · more installs
getsentry/sentry-javascript

Create new skills, modify and improve existing skills, and measure skill performance. Use when …

16 installs
skill-scanner Same source · more installs
getsentry/sentry-javascript

Scan agent skills for security issues. Use when asked to "scan a skill", "audit a skill", "revi…

15 installs
triage-issue Same source · more installs
getsentry/sentry-javascript

Triage GitHub issues with codebase research and actionable recommendations

14 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

upstash-ratelimit-js Similar name
upstash/skills

Rate limiting for serverless and edge apps with the @upstash/ratelimit TypeScript/JavaScript SD…

9.4K installs
dm-limits-and-best-practices Similar name
cognitedata/builder-skills

CDF Data Modeling limits: concurrency (429s), pagination, batching, search vs filter, QueuedTas…

1.9K installs
marketplace-rate-limiting Similar name
vtex/skills

Apply when implementing retry logic, rate limit handling, or resilience patterns in VTEX API in…

765 installs
api-rate-limiting Similar name
aj-geddes/useful-ai-prompts

Implement API rate limiting strategies using token bucket, sliding window, and fixed window alg…

621 installs
freeUnlimited-websearch Similar name
lngu/openclaw-skill-freeunlimited-websearch

Free unlimited web search using DuckDuckGo. No API key required.

564 installs
rate-limiting-implementation Similar name
aj-geddes/useful-ai-prompts

Implement rate limiting, throttling, API quotas, and backpressure mechanisms to protect service…

485 installs

Also in this package

Other skills from getsentry/sentry-javascript · top by installs.

npx skills add getsentry/sentry-javascript
fix-security-vulnerability 20 skill-creator 16 skill-scanner 15 triage-issue 14 e2e 14 add-ai-integration 13 upgrade-dep 13 release 13 dotagents 13 add-cdn-bundle 13

Browse all from getsentry/sentry-javascript

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 8.7K
License LICENSE
Default branch develop
Open issues 634
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,273 B
  • docs SUMMARY.md 355 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 13 installs

SKILL.md

Bump Size Limit

When the size-limit GitHub Action fails, it means one or more bundle scenarios exceed their configured byte thresholds in .size-limit.js. This skill walks through building, measuring, and bumping only the limits that need it.

Workflow

Step 1: Build all packages (including CDN bundles)

A full build is required because size-limit measures the actual compiled artifacts.

yarn build

This takes a few minutes. CDN bundles in packages/browser/build/bundles/ must be up to date — a dev build is not sufficient.

Step 2: Run the size check in JSON mode

yarn test:size-limit

The JSON output is an array of objects. Each object has:

  • name — the scenario label
  • passed — whether it's within the limit
  • size — actual size in bytes
  • sizeLimit — configured limit in bytes

Step 3: Identify failed scenarios

Filter for entries where "passed": false. These are the only ones that need bumping.

Step 4: Calculate new limits

For each failed scenario, round the actual size up to the next full KB (1 KB = 1000 bytes in this context, matching how size-limit interprets the limits in .size-limit.js).

Example: If actual size is 129,127 bytes, the new limit is 130 KB (i.e. 130,000 bytes).

The heuristic is intentionally conservative — it gives just enough headroom without inflating limits unnecessarily.

Step 5: Update .size-limit.js

Open .size-limit.js at the repository root and update the limit field for each failed scenario. Limits are strings like '130 KB'.

Only change limits for scenarios that actually failed. Do not touch passing scenarios.

Step 6: Verify the fix

Re-run size-limit to confirm everything passes:

yarn test:size-limit

If any scenario still fails (e.g., due to rounding edge cases), bump that specific limit by another 1 KB and re-run.