perf-guard

Validate ERP deployment changes against performance regression risks.

Updated May 20, 2025
One-click install
npx skills add https://github.com/lahomsystem/FOMS --skill perf-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perf-guard
Source: https://github.com/lahomsystem/FOMS/tree/main/.cursor/skills/perf-guard
Command: npx skills add https://github.com/lahomsystem/FOMS --skill perf-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents post-deployment ERP performance regressions by enforcing validation gates before code changes are promoted, reducing the risk of slow pages, latency spikes, and hidden scalability failures.

Core Features & Use Cases

  • Performance Regression Gates: Runs guard checks and evaluates deployment risks using automated performance scans and rule-based veto conditions.
  • Diff-Aware Reviews: Maps changed files and patterns to required manual verification steps for caching, database queries, JavaScript loading, and service behavior.
  • Use Case: Use this Skill when preparing an ERP release to identify risky performance changes such as N+1 queries, blocking scripts, unsafe cache invalidation, or inefficient search filters before deployment.

Quick Start

Ask the perf-guard skill to review the current deployment changes and determine whether they are safe to release.

Frequently Asked Questions about perf-guard

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

FAQPage Schema
How do I prevent ERP performance regressions before a production deployment?

To prevent ERP performance regressions before deployment, enforce validation gates that run automated performance scans and apply rule-based veto conditions to block unsafe code changes from reaching production.

What causes post-deployment ERP slowdowns and latency spikes?

Post-deployment ERP slowdowns are caused by risky code changes like N+1 database queries, blocking scripts, unsafe cache invalidation, and inefficient search filters that bypass pre-push performance checks.

How do I run a pre-deployment performance audit for risky database queries and cache changes?

Running a pre-deployment performance audit requires diff-aware reviews that map changed files to manual verification steps for database query optimization, frontend loading behavior, and cache safety verification to identify risks.

Can I use deployment gating checks to block unsafe ERP code changes automatically?

Yes, deployment gating checks can automatically block unsafe ERP code changes by validating modifications against performance scanning rules and trigger-based review procedures to prevent latency spikes before release.