performance-regression-analysis

Performance Regression Analysis (Chinese Version)

When to Use

You need to compare versions or time windows, quantify performance changes, and locate regression risks associated with changes.
You need to conduct a risk review of existing plans, results, or evidence, and form actionable improvement items.
The input is incomplete, but a usable initial version with assumptions and information gaps still needs to be provided first.

The default output is Markdown, suitable for review, execution, and continuous supplementation.
When the user requests a table, CSV, JSON, or ticket format, retain the same risk, evidence, priority, and boundary fields.
If the output will enter an automated process, first confirm the field schema, enum values, and required items.

First read and follow the input, execution rules, minimum coverage checklist, and output order of prompts/performance-regression-analysis.md .
Supplement the scope, environment, version, constraints, evidence, and success criteria that truly affect judgment.
First conduct an input audit, then distinguish confirmed facts, reasonable assumptions, and questions to be confirmed.
Sort by risk and evidence strength, and produce results that can be directly executed, reviewed, or verified.
When information is insufficient, do not stop at asking questions: first deliver a constrained initial version, and explain which conclusions cannot currently hold.

Each execution must read prompts/performance-regression-analysis.md; it is the complete execution specification of this Skill.
When this Skill needs to be evaluated or regressed, read evals/eval.yaml and the matching evals/cases/ use cases.
Only read references/、examples/、scripts/ or output-formats.mdwhen the directory actually exists and the task requires it; do not assume assets that do not exist.

Do not draw regression conclusions when the environment or load is not comparable
Report absolute values and relative changes
Distinguish noise from stable degradation
Do not fabricate system behavior, fields, data, metrics, or root causes that do not exist in the input.
Key conclusions must be linked to evidence; when evidence is insufficient, mark them as assumptions and provide verification methods.
Priority must explain the basis of business impact, likelihood of occurrence, or detectability.

Covered: comparability, latency percentiles, throughput, errors, resource efficiency, statistical fluctuation, change association, user impact.
Facts, assumptions, gaps, and recommendations have been distinguished.
High-risk items have clear priority, evidence, owner, or next step.
The output includes verifiable judgment criteria, rather than vague statements.
No unauthorized production write operations or destructive actions were performed.

Listing only checkpoints without explaining input conditions, expected results, or evidence.
Marking all items as high priority, losing the value of trade-offs.
Replacing domain judgment with tool names or general theory.
Directly refusing when input is incomplete, or conversely pretending that conclusions are already certain.

Start from the paths most likely to cause business loss, security issues, or release blockage.
Use the smallest verifiable experiment to reduce uncertainty, and record reproduction conditions.
Enable the output to be directly executed and reviewed by another engineer.