Performance Regression Gates
Enforces performance standards by preventing bundle size growth and response time regressions in CI/CD.
Install
mkdir -p .claude/skills/performance-regression-gates && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14391" && unzip -o skill.zip -d .claude/skills/performance-regression-gates && rm skill.zipInstalls to .claude/skills/performance-regression-gates
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Gates สำหรับตรวจจับ performance regression ผ่าน benchmarks, bundle size, และ load time monitoringKey capabilities
- →Monitor bundle size to prevent increases
- →Benchmark API response times
- →Enforce Lighthouse performance scores
- →Integrate performance checks into CI pipelines
- →Configure thresholds for various performance metrics
- →Block pull requests if performance regressions are detected
How it works
This skill configures automated gates in a CI pipeline to measure and compare performance metrics like bundle size, response time, and load time against predefined thresholds.
Inputs & outputs
When to use Performance Regression Gates
- →Set bundle size limits
- →Automate API response benchmarking
- →Enforce Lighthouse performance scores
About this skill
Performance Regression Gates
Overview
Gates สำหรับป้องกัน performance regression - bundle size, response time, load time - ต้องไม่แย่ลงเกิน threshold
Why This Matters
- User experience: Slow app = bad UX
- Prevent degradation: จับก่อนถึง users
- Accountability: รู้ว่า PR ไหนทำให้ช้า
- Automated: ไม่ต้องทดสอบ manual
Performance Metrics
1. Bundle Size
# Check bundle size
npm run build
npm run analyze
# Threshold: No >10% increase
Before: 250 KB
After: 260 KB (+4%) ✓ Pass
After: 280 KB (+12%) ✗ Fail
2. Response Time
# API benchmark
npm run benchmark:api
# Threshold: No >20% slower
GET /users: 50ms → 55ms (+10%) ✓ Pass
GET /users: 50ms → 65ms (+30%) ✗ Fail
3. Load Time
# Lighthouse CI
npm run lighthouse
# Threshold: Score ≥90
Performance: 95 ✓ Pass
Performance: 85 ✗ Fail
CI Pipeline
# .github/workflows/performance.yml
name: Performance Gates
on: [pull_request]
jobs:
performance:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Build
run: npm run build
- name: Bundle Size Check
uses: andresz1/size-limit-action@v1
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
limit: 10% # Max 10% increase
- name: Lighthouse CI
uses: treosh/lighthouse-ci-action@v9
with:
runs: 3
assertions:
performance: 90
accessibility: 90
- name: API Benchmark
run: npm run benchmark:api
Configuration
Bundle Size Limit
{
"size-limit": [
{
"path": "dist/bundle.js",
"limit": "250 KB",
"gzip": true
}
]
}
Lighthouse Thresholds
{
"ci": {
"assert": {
"assertions": {
"performance": ["error", {"minScore": 0.9}],
"first-contentful-paint": ["error", {"maxNumericValue": 2000}],
"interactive": ["error", {"maxNumericValue": 3500}]
}
}
}
}
Summary
Performance Gates: ป้องกัน performance regression
Metrics:
- Bundle size: No >10% increase
- Response time: No >20% slower
- Lighthouse: Score ≥90
Tools:
- size-limit (bundle)
- Lighthouse CI (load time)
- Custom benchmarks (API)
Action: Block merge if regression detected
When not to use it
- →When performance metrics are not a concern for the project
- →When the project does not have a CI/CD pipeline
- →When manual performance testing is preferred
Limitations
- →Performance metrics are limited to bundle size, response time, and Lighthouse scores
- →Thresholds must be manually configured for each metric
- →Requires specific tools like size-limit and Lighthouse CI for implementation
How it compares
This skill automates performance regression detection within the CI pipeline, providing immediate feedback and blocking deployments, unlike manual testing that occurs post-development.
Compared to similar skills
Performance Regression Gates side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| Performance Regression Gates (this skill) | 0 | 2mo | Review | Intermediate |
| service-mesh-observability | 5 | 2mo | No flags | Advanced |
| sentry-release-management | 1 | 29d | Caution | Intermediate |
| sentry-performance-tracing | 1 | 29d | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by majiayu000
View all by majiayu000 →You might also like
service-mesh-observability
wshobson
Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debugging latency issues, or implementing SLOs for service communication.
sentry-release-management
jeremylongshore
Manage Sentry releases and associate commits. Use when creating releases, tracking commits, or managing release artifacts. Trigger with phrases like "sentry release", "sentry commits", "manage sentry versions", "sentry release workflow".
sentry-performance-tracing
jeremylongshore
Execute set up performance monitoring and distributed tracing with Sentry. Use when implementing performance tracking, tracing requests, or monitoring application performance. Trigger with phrases like "sentry performance", "sentry tracing", "sentry APM", "monitor performance sentry".
analyze-ci-speed
Sovereign-Labs
Analyze compilation time and test durations from CI logs. Use when the user asks about slow builds, slow tests, or wants to optimize CI time.
observability
devartblake
Use this skill for logs, metrics, tracing, health checks, and dashboards.
performance-monitor
adiytharpansa
Real-time monitoring and optimization of system performance. Use when you need to track response times, resource usage, skill efficiency, and overall system health. This skill enables continuous performance optimization, bottleneck detection, and proactive improvements to keep OpenClaw running at pe