[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M799FST3488ZJ4FS8MM5EP1W":3,"skill-same:01M799FST3488ZJ4FS8MM5EP1W":55},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M799FST3488ZJ4FS8MM5EP1W","tracking-regression-tests",null,"Track and manage regression test suites across releases.\nUse when performing specialized testing.\nTrigger with phrases like \"track regressions\", \"manage regression suite\", or \"validate against baseline\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftesting--regression-test-tracker--tracking-regression-tests\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tracking-regression-tests\ndescription: |\n  Track and manage regression test suites across releases.\n  Use when performing specialized testing.\n  Trigger with phrases like \"track regressions\", \"manage regression suite\", or \"validate against baseline\".\n\nallowed-tools: Read, Write, Edit, Grep, Glob, Bash(test:regression-*)\nversion: 1.0.0\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\nlicense: MIT\ncompatible-with: claude-code, codex, openclaw\ntags: [testing, tracking-regression]\n---\n# Regression Test Tracker\n\n## Overview\n\nTrack, manage, and maintain regression test suites across releases to ensure previously fixed bugs stay fixed and existing features remain stable. Maps regression tests to bug tickets, monitors test health over time, and identifies gaps where fixed bugs lack corresponding regression tests.\n\n## Prerequisites\n\n- Test framework with tagging or marking support (`@tag`, `pytest.mark`, JUnit `@Tag`)\n- Bug tracking system with issue IDs (GitHub Issues, Jira, Linear)\n- Git history accessible for correlating bug fixes with test additions\n- Existing test suite with named test cases\n- CI pipeline producing test result artifacts (JUnit XML or JSON)\n\n## Instructions\n\n1. Scan the codebase with Grep for bug-fix commits by searching commit messages for patterns like `fix:`, `bugfix`, `closes #`, or Jira ticket IDs.\n2. For each bug-fix commit, check whether a corresponding regression test exists:\n   - Search test files for the bug ticket ID in test names, comments, or tags.\n   - Verify the test exercises the specific code path that was fixed.\n   - Flag fixes without regression tests as coverage gaps.\n3. Create a regression test inventory file (`regression-tests.json` or `regression-tests.md`) mapping:\n   - Bug ticket ID to test file and test name.\n   - Severity of the original bug (critical, high, medium, low).\n   - Date the regression test was added.\n   - Current test status (passing, failing, skipped).\n4. Tag existing regression tests with metadata for traceability:\n   - Jest: Add `\u002F\u002F @regression BUG-123` comments or use `describe.each` with ticket data.\n   - pytest: Apply `@pytest.mark.regression` and `@pytest.mark.bug(\"BUG-123\")` markers.\n   - JUnit: Use `@Tag(\"regression\")` and `@DisplayName(\"BUG-123: description\")`.\n5. Generate a regression coverage report showing:\n   - Total bugs fixed vs. bugs with regression tests (coverage percentage).\n   - Untested regressions ranked by severity.\n   - Tests that have become flaky or were disabled.\n6. Set up a CI check that fails the build if a bug-fix PR does not include at least one regression test.\n7. Schedule periodic audits (weekly or per-release) to verify all regression tests still pass and remain relevant.\n\n## Output\n\n- Regression test inventory file mapping bugs to tests\n- Tagged test files with regression markers and ticket references\n- Coverage gap report listing bug fixes without regression tests\n- CI configuration for regression test enforcement\n- Release readiness checklist based on regression suite pass rate\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|---------|\n| Regression test passes but bug reappears | Test does not cover the exact failure condition | Review the original bug report; update the test to assert against the specific edge case |\n| Orphaned regression tags | Bug ticket was closed as duplicate or invalid | Audit tags quarterly; remove or reassign tests for invalid tickets |\n| Regression test consistently skipped | Test marked as `skip` due to environment issues | Fix the environment dependency or convert to an integration test with proper setup |\n| False coverage gap | Bug was fixed by a refactor that removed the vulnerable code path | Mark as \"resolved by removal\" in the inventory; add a comment explaining why no test is needed |\n| Flaky regression test | Non-deterministic timing or data dependency | Stabilize with retries, fixed seeds, or mocked clocks; tag as `@flaky` for monitoring |\n\n## Examples\n\n**pytest regression test with marker:**\n```python\nimport pytest\n\n@pytest.mark.regression\n@pytest.mark.bug(\"GH-1042\")  # 1042 = configured value\ndef test_csv_export_handles_unicode_characters():\n    \"\"\"Regression: GH-1042 -- CSV export crashed on non-ASCII names.\"\"\"\n    result = export_csv([{\"name\": \"Rene\"}])\n    assert \"Rene\" in result\n    assert result.startswith(\"name\\n\")\n```\n\n**Jest regression test with ticket reference:**\n```typescript\ndescribe('BUG-789: Cart total calculation', () => {  # 789 = configured value\n  it('applies percentage discount before tax', () => {\n    const cart = createCart([{ price: 100, qty: 2 }]);\n    cart.applyDiscount({ type: 'percent', value: 10 });\n    expect(cart.subtotal).toBe(180);\n    expect(cart.tax).toBe(18); \u002F\u002F 10% tax on discounted subtotal\n  });\n});\n```\n\n**Regression inventory entry:**\n```json\n{\n  \"BUG-1042\": {  # 1042 = configured value\n    \"test_file\": \"tests\u002Ftest_export.py::test_csv_export_handles_unicode_characters\",\n    \"severity\": \"high\",\n    \"added\": \"2026-01-15\",  # 2026 year\n    \"status\": \"passing\"\n  }\n}\n```\n\n## Resources\n\n- pytest markers: https:\u002F\u002Fdocs.pytest.org\u002Fen\u002Fstable\u002Fhow-to\u002Fmark.html\n- JUnit 5 tags: https:\u002F\u002Fjunit.org\u002Fjunit5\u002Fdocs\u002Fcurrent\u002Fuser-guide\u002F#writing-tests-tagging-and-filtering\n- Jest describe\u002Ftest organization: https:\u002F\u002Fjestjs.io\u002Fdocs\u002Fapi#describename-fn\n- Regression testing best practices: https:\u002F\u002Fmartinfowler.com\u002Fbliki\u002FSelfTestingCode.html","# Regression Test Tracker\n\n## Overview\n\nTrack, manage, and maintain regression test suites across releases to ensure previously fixed bugs stay fixed and existing features remain stable. Maps regression tests to bug tickets, monitors test health over time, and identifies gaps where fixed bugs lack corresponding regression tests.\n\n## Prerequisites\n\n- Test framework with tagging or marking support (`@tag`, `pytest.mark`, JUnit `@Tag`)\n- Bug tracking system with issue IDs (GitHub Issues, Jira, Linear)\n- Git history accessible for correlating bug fixes with test additions\n- Existing test suite with named test cases\n- CI pipeline producing test result artifacts (JUnit XML or JSON)\n\n## Instructions\n\n1. Scan the codebase with Grep for bug-fix commits by searching commit messages for patterns like `fix:`, `bugfix`, `closes #`, or Jira ticket IDs.\n2. For each bug-fix commit, check whether a corresponding regression test exists:\n   - Search test files for the bug ticket ID in test names, comments, or tags.\n   - Verify the test exercises the specific code path that was fixed.\n   - Flag fixes without regression tests as coverage gaps.\n3. Create a regression test inventory file (`regression-tests.json` or `regression-tests.md`) mapping:\n   - Bug ticket ID to test file and test name.\n   - Severity of the original bug (critical, high, medium, low).\n   - Date the regression test was added.\n   - Current test status (passing, failing, skipped).\n4. Tag existing regression tests with metadata for traceability:\n   - Jest: Add `\u002F\u002F @regression BUG-123` comments or use `describe.each` with ticket data.\n   - pytest: Apply `@pytest.mark.regression` and `@pytest.mark.bug(\"BUG-123\")` markers.\n   - JUnit: Use `@Tag(\"regression\")` and `@DisplayName(\"BUG-123: description\")`.\n5. Generate a regression coverage report showing:\n   - Total bugs fixed vs. bugs with regression tests (coverage percentage).\n   - Untested regressions ranked by severity.\n   - Tests that have become flaky or were disabled.\n6. Set up a CI check that fails the build if a bug-fix PR does not include at least one regression test.\n7. Schedule periodic audits (weekly or per-release) to verify all regression tests still pass and remain relevant.\n\n## Output\n\n- Regression test inventory file mapping bugs to tests\n- Tagged test files with regression markers and ticket references\n- Coverage gap report listing bug fixes without regression tests\n- CI configuration for regression test enforcement\n- Release readiness checklist based on regression suite pass rate\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|---------|\n| Regression test passes but bug reappears | Test does not cover the exact failure condition | Review the original bug report; update the test to assert against the specific edge case |\n| Orphaned regression tags | Bug ticket was closed as duplicate or invalid | Audit tags quarterly; remove or reassign tests for invalid tickets |\n| Regression test consistently skipped | Test marked as `skip` due to environment issues | Fix the environment dependency or convert to an integration test with proper setup |\n| False coverage gap | Bug was fixed by a refactor that removed the vulnerable code path | Mark as \"resolved by removal\" in the inventory; add a comment explaining why no test is needed |\n| Flaky regression test | Non-deterministic timing or data dependency | Stabilize with retries, fixed seeds, or mocked clocks; tag as `@flaky` for monitoring |\n\n## Examples\n\n**pytest regression test with marker:**\n```python\nimport pytest\n\n@pytest.mark.regression\n@pytest.mark.bug(\"GH-1042\")  # 1042 = configured value\ndef test_csv_export_handles_unicode_characters():\n    \"\"\"Regression: GH-1042 -- CSV export crashed on non-ASCII names.\"\"\"\n    result = export_csv([{\"name\": \"Rene\"}])\n    assert \"Rene\" in result\n    assert result.startswith(\"name\\n\")\n```\n\n**Jest regression test with ticket reference:**\n```typescript\ndescribe('BUG-789: Cart total calculation', () => {  # 789 = configured value\n  it('applies percentage discount before tax', () => {\n    const cart = createCart([{ price: 100, qty: 2 }]);\n    cart.applyDiscount({ type: 'percent', value: 10 });\n    expect(cart.subtotal).toBe(180);\n    expect(cart.tax).toBe(18); \u002F\u002F 10% tax on discounted subtotal\n  });\n});\n```\n\n**Regression inventory entry:**\n```json\n{\n  \"BUG-1042\": {  # 1042 = configured value\n    \"test_file\": \"tests\u002Ftest_export.py::test_csv_export_handles_unicode_characters\",\n    \"severity\": \"high\",\n    \"added\": \"2026-01-15\",  # 2026 year\n    \"status\": \"passing\"\n  }\n}\n```\n\n## Resources\n\n- pytest markers: https:\u002F\u002Fdocs.pytest.org\u002Fen\u002Fstable\u002Fhow-to\u002Fmark.html\n- JUnit 5 tags: https:\u002F\u002Fjunit.org\u002Fjunit5\u002Fdocs\u002Fcurrent\u002Fuser-guide\u002F#writing-tests-tagging-and-filtering\n- Jest describe\u002Ftest organization: https:\u002F\u002Fjestjs.io\u002Fdocs\u002Fapi#describename-fn\n- Regression testing best practices: https:\u002F\u002Fmartinfowler.com\u002Fbliki\u002FSelfTestingCode.html",{"name":5,"tags":24,"author":27,"license":15,"version":28,"description":29,"allowed-tools":30,"compatible-with":31},[25,26],"testing","tracking-regression","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Track and manage regression test suites across releases.\nUse when performing specialized testing.\nTrigger with phrases like \"track regressions\", \"manage regression suite\", or \"validate against baseline\".\n","Read, Write, Edit, Grep, Glob, Bash(test:regression-*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Ftesting--regression-test-tracker--tracking-regression-tests",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill tracking-regression-tests",{"tool":47,"command":48},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill tracking-regression-tests",{"tool":50,"command":51},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill tracking-regression-tests","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftesting--regression-test-tracker--tracking-regression-tests\u002FSKILL.md",true,[],[56,63,70,77,84,92],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]