skills.rest
moongci38-oss
moongci38-ossCOMMUNITY
Explore all skills by this author →
GitHub

benchmark

Compare feature branch bundle size, test time, and API response time against a develop baseline.

Updated Jun 3, 2026
Search Tags:#code review#pull request#feature branch#performance benchmarking#performance regression
One-click install
npx skills add https://github.com/moongci38-oss/forge-plugins --skill benchmark-moongci38-oss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/moongci38-oss/forge-plugins/tree/main/forge-build/skills/benchmark
Command: npx skills add https://github.com/moongci38-oss/forge-plugins --skill benchmark-moongci38-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the performance benchmarking of feature branches against a develop baseline, ensuring code quality and performance before merging.

Core Features & Use Cases

  • Automated Benchmarking: Measures and compares the performance metrics of a feature branch against the develop branch.
  • Performance Metrics: Tracks bundle size, test time, and API response time.
  • Use Case: Before merging a pull request, use the benchmark skill to compare the performance of the feature branch with the develop branch to catch performance regressions early.

Quick Start

Run the /benchmark command to compare the performance of the current feature branch against the develop branch.

Frequently Asked Questions about benchmark

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate performance benchmarking for a feature branch before merging?▼

To automate performance benchmarking before merging, run the benchmark command to compare the feature branch against a develop baseline. This automatically measures bundle size, test time, and API response time to catch regressions during code reviews.

What is the best way to catch performance regressions in a pull request workflow?▼

The best way to catch performance regressions in a pull request workflow is to use automated benchmarking. By comparing feature branch metrics like test time and API response time against a develop baseline, regressions are identified before merging.

Do I need any external dependencies to run performance benchmarking on my code?▼

No external dependencies are required to run performance benchmarking on your code. The skill operates independently using Git operations to measure and compare feature branch performance against the develop baseline.

How to track test time and bundle size differences during code reviews?▼

To track test time and bundle size differences during code reviews, run the benchmark command. It provides automated feedback on performance regressions by comparing the feature branch's metrics directly against the develop branch baseline.

Related Skills

Explore More Software Engineering Skills→
smallorbitsmallorbit

create-branch

Create and checkout Git branches from origin/develop.

Community
Intermediate
BEIRUXBEIRUX

vercel-react-best-practices

Optimize React and Next.js data fetching and bundle size in code reviews.

Official
Advanced
llmh333llmh333

benchmark

Measure browser Core Web Vitals and API latency percentiles against JSON baselines.

Community
Intermediate
R2W1csR2W1cs
1

performance-profiling

Run Lighthouse audits to analyze web app performance and core web vitals.

Community
Advanced