[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77S1RNBFCWAT9DYNEDKFG35":3,"skill-same:01M77S1RNBFCWAT9DYNEDKFG35":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M77S1RNBFCWAT9DYNEDKFG35","regression-testing",null,"Execute regression testing to verify that new changes have not introduced defects into existing functionality before release.","panksooungman-dot\u002FAI-Web-Master","panksooungman-dot","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263377190?v=4","01M77RQKZAR08JG1JSWP1MVXPV","cnbiz","01M77RQM00YBBJX4F6Y04HT8RN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Fquality\u002Fregression-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: regression-testing\ndescription: Execute regression testing to verify that new changes have not introduced defects into existing functionality before release.\nversion: 1.0.0\nauthor: AI Business OS\nlicense: MIT\ncategory: workflow\npriority: required\n---\n\n# Regression Testing\n\n## Purpose\n\nThis skill validates that recent code changes have not negatively impacted existing functionality.\n\nThe objective is to ensure application stability, maintain user confidence, and prevent regressions before deployment.\n\nRegression testing should be performed after bug fixes, feature additions, refactoring, dependency updates, and release candidates.\n\n---\n\n# When to Use\n\nExecute after:\n\n- quality\u002Fbug-triage\n\nExecute before:\n\n- release\u002Fdeployment\n\n---\n\n# Objectives\n\nVerify that:\n\n- Existing features continue to work\n- Fixed defects remain resolved\n- Critical user flows are stable\n- No unintended side effects exist\n- Release quality is maintained\n\n---\n\n# Inputs\n\nExpected inputs:\n\n- Test Plan\n- Test Cases\n- Bug Fixes\n- Integrated Application\n- Release Candidate\n- Previous Test Results\n\n---\n\n# Regression Scope\n\nCover:\n\n- Authentication\n- Authorization\n- User Management\n- Dashboard\n- Navigation\n- Forms\n- CRUD Operations\n- Search\n- Notifications\n- Payments\n- External Integrations\n\nPrioritize business-critical functionality.\n\n---\n\n# Test Coverage\n\nVerify:\n\n- Previously fixed bugs\n- Core business workflows\n- High-risk modules\n- Shared components\n- Common user journeys\n- Cross-module interactions\n\nFocus first on areas affected by recent changes.\n\n---\n\n# Execution Strategy\n\nPerform:\n\n- Automated Regression Tests\n- Manual Regression Tests\n- Smoke Verification\n- Cross-browser Testing\n- Responsive Testing\n\nUse automation whenever practical.\n\n---\n\n# Test Environment\n\nEnsure:\n\n- Environment matches production\n- Test data is prepared\n- External services are available or mocked\n- Configuration is validated\n\n---\n\n# Result Classification\n\nRecord results as:\n\n- Passed\n- Failed\n- Blocked\n- Skipped\n\nEvery failed test should reference a tracked defect.\n\n---\n\n# Defect Handling\n\nWhen failures occur:\n\n- Document the issue\n- Assign severity\n- Link affected feature\n- Notify responsible owner\n- Re-test after the fix\n\nRegression failures must be resolved before release unless explicitly accepted.\n\n---\n\n# Release Readiness\n\nConfirm:\n\n- No unresolved critical defects\n- All critical regression tests passed\n- High-priority defects addressed\n- Product Owner approval obtained (if required)\n\n---\n\n# Workflow\n\n```text\nReview Release Candidate\n\n↓\n\nSelect Regression Suite\n\n↓\n\nPrepare Environment\n\n↓\n\nExecute Automated Tests\n\n↓\n\nExecute Manual Tests\n\n↓\n\nRecord Results\n\n↓\n\nReport Defects\n\n↓\n\nVerify Fixes\n\n↓\n\nApprove Release\n```\n\n---\n\n# Outputs\n\nGenerate:\n\n- Regression Test Report\n- Test Execution Summary\n- Defect Summary\n- Coverage Report\n- Release Readiness Report\n\n---\n\n# Validation Checklist\n\nBefore completion verify:\n\n- Critical regression suite passed\n- Previously fixed defects verified\n- No new critical issues introduced\n- Test evidence documented\n- Release readiness confirmed\n\n---\n\n# Failure Conditions\n\nStop release if:\n\n- Critical regression tests fail\n- Core user journeys are broken\n- High-severity defects remain unresolved\n- Test environment is invalid\n- Required regression coverage is incomplete\n\n---\n\n# Rules\n\n- Always execute regression tests before release.\n- Prioritize high-risk and business-critical workflows.\n- Re-test all resolved defects.\n- Keep regression suites up to date.\n- Record reproducible evidence for every failure.\n\n---\n\n# Success Criteria\n\nThis skill succeeds when:\n\n- all critical regression tests pass\n- no release-blocking regressions exist\n- product stability is verified\n- the application is approved for deployment\n\n---\n\n# Next Skills\n\n```text\nrelease\u002Fdeployment\n\n↓\n\nrelease\u002Fmonitoring\n\n↓\n\nrelease\u002Frollback\n```\n\n---\n\n# Related Skills\n\n- testing\n- bug-triage\n- code-review\n- security-review\n- performance\n- deployment\n\n---\n\n# Version History\n\n| Version | Date | Description |\n|---------|------|-------------|\n| 1.0.0 | 2026-07-10 | Initial release |","# Regression Testing\n\n## Purpose\n\nThis skill validates that recent code changes have not negatively impacted existing functionality.\n\nThe objective is to ensure application stability, maintain user confidence, and prevent regressions before deployment.\n\nRegression testing should be performed after bug fixes, feature additions, refactoring, dependency updates, and release candidates.\n\n---\n\n# When to Use\n\nExecute after:\n\n- quality\u002Fbug-triage\n\nExecute before:\n\n- release\u002Fdeployment\n\n---\n\n# Objectives\n\nVerify that:\n\n- Existing features continue to work\n- Fixed defects remain resolved\n- Critical user flows are stable\n- No unintended side effects exist\n- Release quality is maintained\n\n---\n\n# Inputs\n\nExpected inputs:\n\n- Test Plan\n- Test Cases\n- Bug Fixes\n- Integrated Application\n- Release Candidate\n- Previous Test Results\n\n---\n\n# Regression Scope\n\nCover:\n\n- Authentication\n- Authorization\n- User Management\n- Dashboard\n- Navigation\n- Forms\n- CRUD Operations\n- Search\n- Notifications\n- Payments\n- External Integrations\n\nPrioritize business-critical functionality.\n\n---\n\n# Test Coverage\n\nVerify:\n\n- Previously fixed bugs\n- Core business workflows\n- High-risk modules\n- Shared components\n- Common user journeys\n- Cross-module interactions\n\nFocus first on areas affected by recent changes.\n\n---\n\n# Execution Strategy\n\nPerform:\n\n- Automated Regression Tests\n- Manual Regression Tests\n- Smoke Verification\n- Cross-browser Testing\n- Responsive Testing\n\nUse automation whenever practical.\n\n---\n\n# Test Environment\n\nEnsure:\n\n- Environment matches production\n- Test data is prepared\n- External services are available or mocked\n- Configuration is validated\n\n---\n\n# Result Classification\n\nRecord results as:\n\n- Passed\n- Failed\n- Blocked\n- Skipped\n\nEvery failed test should reference a tracked defect.\n\n---\n\n# Defect Handling\n\nWhen failures occur:\n\n- Document the issue\n- Assign severity\n- Link affected feature\n- Notify responsible owner\n- Re-test after the fix\n\nRegression failures must be resolved before release unless explicitly accepted.\n\n---\n\n# Release Readiness\n\nConfirm:\n\n- No unresolved critical defects\n- All critical regression tests passed\n- High-priority defects addressed\n- Product Owner approval obtained (if required)\n\n---\n\n# Workflow\n\n```text\nReview Release Candidate\n\n↓\n\nSelect Regression Suite\n\n↓\n\nPrepare Environment\n\n↓\n\nExecute Automated Tests\n\n↓\n\nExecute Manual Tests\n\n↓\n\nRecord Results\n\n↓\n\nReport Defects\n\n↓\n\nVerify Fixes\n\n↓\n\nApprove Release\n```\n\n---\n\n# Outputs\n\nGenerate:\n\n- Regression Test Report\n- Test Execution Summary\n- Defect Summary\n- Coverage Report\n- Release Readiness Report\n\n---\n\n# Validation Checklist\n\nBefore completion verify:\n\n- Critical regression suite passed\n- Previously fixed defects verified\n- No new critical issues introduced\n- Test evidence documented\n- Release readiness confirmed\n\n---\n\n# Failure Conditions\n\nStop release if:\n\n- Critical regression tests fail\n- Core user journeys are broken\n- High-severity defects remain unresolved\n- Test environment is invalid\n- Required regression coverage is incomplete\n\n---\n\n# Rules\n\n- Always execute regression tests before release.\n- Prioritize high-risk and business-critical workflows.\n- Re-test all resolved defects.\n- Keep regression suites up to date.\n- Record reproducible evidence for every failure.\n\n---\n\n# Success Criteria\n\nThis skill succeeds when:\n\n- all critical regression tests pass\n- no release-blocking regressions exist\n- product stability is verified\n- the application is approved for deployment\n\n---\n\n# Next Skills\n\n```text\nrelease\u002Fdeployment\n\n↓\n\nrelease\u002Fmonitoring\n\n↓\n\nrelease\u002Frollback\n```\n\n---\n\n# Related Skills\n\n- testing\n- bug-triage\n- code-review\n- security-review\n- performance\n- deployment\n\n---\n\n# Version History\n\n| Version | Date | Description |\n|---------|------|-------------|\n| 1.0.0 | 2026-07-10 | Initial release |",{"name":5,"author":24,"license":15,"version":25,"category":26,"priority":27,"description":7},"AI Business OS","1.0.0","workflow","required","main","8ba4c8c0d58db28bdcfccd02e7d75b7a3cf70dc9","skills\u002Fworkflows\u002Fquality\u002Fregression-testing","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master","https:\u002F\u002Fai-web-master-cnbiz-web.vercel.app","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot","2026-11-14 20:43:00",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add panksooungman-dot\u002FAI-Web-Master --skill regression-testing",{"tool":41,"command":42},"bunx","bunx skills add panksooungman-dot\u002FAI-Web-Master --skill regression-testing",{"tool":44,"command":45},"pnpm","pnpm dlx skills add panksooungman-dot\u002FAI-Web-Master --skill regression-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Fquality\u002Fregression-testing\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M77S2FHFC73NY664GYHNHGE8","rollback","Plan, validate, and execute safe rollback procedures to restore a stable system state when deployments introduce critical issues.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Frollback\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M77S2C5NW59NY9F939ECFVN0","release-note","Create clear, concise, and stakeholder-friendly release notes that communicate new features, improvements, fixes, breaking changes, and operational guidance for each release.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Frelease-note\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M77S28YMHR597AZF39CR0CNG","monitoring","Continuously observe application health, performance, reliability, and business metrics after deployment to detect issues early and support operational excellence.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Fmonitoring\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M77S26FGE7P6W5MDSBQ1WTPV","maintenance","Maintain, improve, and support production systems after release through continuous monitoring, issue resolution, updates, and operational excellence.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Fmaintenance\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M77S24CZGKFZEXXS3N0B067G","deployment","Plan, validate, and execute application deployments safely and consistently across environments while minimizing downtime and deployment risk.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Fdeployment\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M77S21AG798PAEH5HEVYBYF7","changelog","Maintain a structured, accurate, and versioned changelog that records all notable changes made to the project across releases.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Fchangelog\u002FSKILL.md",[],[]]