regression-check
From the author
Compare current behavior against baseline to detect regressions
Install
npx skills add jmagly/aiwg --skill regression-check -a claude-code
Installs to .claude/skills/regression-check/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 85
Security100
Provenance68
Maintenance100
Licence100
Adoption40
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- detecting-performance-regressionsforyourhealth111-pixel/Vibe-SkillsCompare current benchmark results against historical baselines to spot performance regressions. Use as an explicit/manual helper for build-to-build degradation review, not for broad optimization strategy or low-level profiling ownership.Engineering★ 3.8K
- benchmarkhashgraph-online/awesome-codex-pluginsUse this skill to measure performance baselines, detect regressions before/after PRs, and compare stack alternatives.Other★ 1.4K
- hunt-regressionstrailofbits/skillsUse when discovering possible regressions from a pinned change and its callers before reproduction.Other★ 7.8K
- metacognitive-self-modathola/claude-night-marketAnalyze and improve the improvement process. Use for detecting regressions and meta-optimization.Other★ 343
- recall-reasoningparcadei/Continuous-Claude-v3Search past reasoning for relevant decisions and approachesOther★ 3.9K
- regression-consistency-checkerArabelaTso/Skills-4-SEChecks whether a new version of a repository preserves the behavior observed by tests on the old version. Use this skill when comparing two versions of code to detect regressions, verify refactoring safety, validate bug fixes don't break existing functionality, or ensure backward compatibility. Detects differences in function outputs, exceptions, observable states, and performance between versions. Generates reports highlighting potential regressions (critical, high, medium, low severity), improvements, and areas requiring verification. Triggers when users ask to check for regressions between versions, compare test behavior across versions, verify behavior preservation, or validate that changes don't break existing tests.Testing★ 259
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in