Regression Testing

Name: Regression Testing
Author: proffesor-for-testing

Checked

proffesor-for-testing·vlatest·testing·MIT

Automatically re-runs previously failed test cases to verify fixes and prevent regressions.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add proffesor-for-testing/agentic-qe --skill regression-testing -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

proffesor-for-testing

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 11 Oct 2026

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned proffesor-for-testing/agentic-qe at 124d8c735e.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 124d8c735e
Manifest: assets/skills/regression-testing/SKILL.md
Scanned: 8 files, 2,112 lines
Copies in repo: 2 — all of them scanned

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

The regression-testing skill enables AI agents to automatically re-run test suites after code changes to ensure new updates do not break existing functionality. It systematically validates that software behavior remains consistent across different scenarios following modifications.

When to use it

After deploying a new feature or patch to verify no unintended side effects occurred.
Before merging pull requests to catch regressions early in the development cycle.
Following infrastructure or configuration changes that might impact application stability.
During continuous integration pipelines to maintain a reliable build status.

Key capabilities

Executes predefined test suites automatically upon detecting code updates.
Compares current system behavior against baseline expectations to identify failures.
Reports specific details on which tests passed or failed after the change.

Example prompts

"Run the regression test suite for the authentication module after my latest commit."
"Check if the recent database schema update broke any existing user login flows using regression testing."
"Execute full regression tests and summarize any failures caused by the new API endpoint."

Tips & gotchas

Ensure your test environment mirrors production closely to avoid false positives or negatives. Maintain a clear baseline of passing tests so the agent can accurately detect deviations caused by new changes.