guard-regression
Guard Refactors Against Regression
Refactoring can hide test failures, build breaks, and quality drops. This skill records baselines, reruns checks, compares results, and recommends rollback when quality drops.
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "guard-regression" from https://skillstore.io/skills/crearize-guard-regression.md and its manifest at https://skillstore.io/api/skills/crearize-guard-regression/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "guard-regression". Compare the post-refactor checks with the saved baseline.
Expected outcome:
- Regression status: no regression detected.
- Tests, lint, build, and coverage stayed at or above baseline.
- Next action: approve the refactor report.
Using "guard-regression". The backend build failed after refactoring.
Expected outcome:
- Regression status: severe regression detected.
- The build result changed from success to failure.
- Next action: recommend immediate rollback and rerun validation after rollback.
Using "guard-regression". Coverage dropped by three percent after cleanup.
Expected outcome:
- Regression status: minor regression warning.
- Coverage dropped within the warning range.
- Next action: request review before accepting the refactor.
Security Audit
SafeThe static backtick findings are Markdown fences and inline path references, not executable Ruby backtick expressions. The skill documents local Gradle and pnpm verification commands, but no obfuscation, exfiltration, prompt injection, or destructive behavior was found.
Risk Factors
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/crearize-guard-regression/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/crearize-guard-regression?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/crearize-guard-regression?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/crearize-guard-regression/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/crearize-guard-regression.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Crearize. (2026). guard-regression security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/crearize-guard-regression/audits/9BibTeX citation
@techreport{crearize-crearize-guard-regression-2026,
author = {Crearize},
title = {guard-regression security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/crearize-guard-regression/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "guard-regression security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "Crearize"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/crearize-guard-regression/audits/9"
identifiers:
- type: other
value: "skillstore:crearize-guard-regression:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Validate Refactoring Safety
Compare pre-refactor and post-refactor quality results before accepting a change.
Create Regression Reports
Summarize tests, lint, build status, and coverage in a review-ready format.
Decide Rollback Timing
Use strict criteria to decide whether a regression needs immediate rollback.
Try These Prompts
Use guard-regression to record current backend and frontend quality results before refactoring starts.
Use guard-regression to rerun the documented checks and compare them with the saved baseline.
Use guard-regression to identify which metrics degraded and prepare a rollback recommendation.
Use guard-regression to evaluate test, lint, build, coverage, and performance results against rollback criteria.
Best Practices
- Capture the baseline before any refactoring begins.
- Run the same checks in the same environment for fair comparison.
- Record exact counts and percentages in every report.
Avoid
- Do not compare results from different environments without noting the difference.
- Do not ignore a new test failure because other metrics improved.
- Do not approve a refactor when the build changed from success to failure.