Menu
Run regression testing suite to verify existing functionality still works after changes
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Creates well-structured Claude Skills with proper YAML frontmatter, clear instructions, and supporting files. Activates when the user wants to create a new skill, add capabilities to their AI assistant, encode team preferences, or structure any reusable instruction set. Covers the full lifecycle from intent capture through writing, testing, and refinement.
Shows all available skills, platform support, common workflows, and troubleshooting for the @terrazul/assistant-creator package. Activates when the user asks for help, wants to know what's available, or needs guidance on using the package.
Interactive wizard to set up MCP server credentials in your shell environment (~/.zshenv, ~/.bashrc, etc.). Activates when the user needs to configure API keys, tokens, or environment variables for MCP servers, or after adding new MCP integrations that require authentication.
Searches mcp.so marketplace for MCP servers and configures them for Claude, Codex, or Gemini. Use when user wants to add external tool integrations, find MCP servers, or configure model context protocol.
Converts Claude SKILL.md files to Gemini-compatible format. Use when user wants to use a Claude skill with Gemini CLI, or needs to make skills cross-platform compatible.
Create well-formed Claude agents with proper YAML frontmatter, system prompts, and examples. Use when user wants to create a new agent, customize Claude behavior, or needs help structuring an agent definition.
| name | regression-test |
| description | Run regression testing suite to verify existing functionality still works after changes |
Validates that existing functionality continues to work correctly after code changes, deployments, or dependency updates.
Determine regression scope based on changes:
Establish expected behavior:
Organize tests by priority:
P0 - Critical Path (Always Run)
P1 - Important Features
P2 - Edge Cases
Execute tests systematically:
Compare results to baseline:
Generate regression report:
Essential functionality that must work:
Verify fixes haven't regressed:
Test system interactions:
Check performance hasn't degraded:
Use the regression-test skill to run full regression suite before the v2.0 release
Use the regression-test skill to test user authentication after the password reset changes were deployed
Use the regression-test skill for a quick smoke test before the demo
Use the regression-test skill to verify the login fix and ensure no regressions in authentication
# Regression Test Report
**Build/Version**: [Version]
**Date**: [Date]
**Scope**: Full / Targeted / Smoke
**Baseline**: [Previous test date/version]
## Summary
| Metric | Count |
|--------|-------|
| Tests Executed | X |
| Passed | X |
| Failed | X |
| New Failures | X |
| Fixed (Newly Passing) | X |
## Regression Status: PASS / FAIL
## New Failures (Regressions)
[List of tests that were passing but now fail]
## Fixed Issues (Newly Passing)
[List of tests that were failing but now pass]
## Unchanged Failures
[Known failures that remain - verify they're expected]
## Recommendation
[Ship / Block / Investigate]