{"enrichment":{"faq":[{"a":"test-fixing identifies all failing tests, groups them by error type and root cause, then fixes them in priority order. It handles infrastructure issues first (imports, dependencies), then API changes, then logic bugs. After each fix group passes, it moves to the next until the full suite succeeds.","q":"How does test-fixing fix failing tests systematically?"},{"a":"test-fixing repairs broken test suites after code refactoring or API changes by analyzing which tests broke and why. It prioritizes failures by module and error category, then applies targeted fixes to restore the suite systematically rather than attempting random corrections.","q":"What should I do when tests are failing after refactor?"},{"a":"test-fixing identifies and prioritizes test failures by error type and affected modules, grouping similar errors together. This grouping reveals root causes\u2014whether infrastructure, API, or logic issues\u2014so fixes address the underlying problem rather than symptoms, preventing cascading failures.","q":"How can test-fixing identify and fix test failures?"},{"a":"Yes. test-fixing resolves CI/CD pipeline failures caused by test suite breakage by systematically repairing the underlying test failures. Once grouped errors are fixed in priority order and focused test runs verify each fix, the pipeline can resume.","q":"Can test-fixing resolve CI/CD pipeline failures from broken tests?"},{"a":"test-fixing verifies test fixes and prevents regressions by running focused test suites after each fix group passes. This ensures each correction actually resolves its error category before moving to the next, catching any new breakage early.","q":"How does test-fixing prevent regressions after fixing tests?"}],"shadow_tags":["error-grouping","test-debugging","failure-analysis","systematic-repair","ci-cd-failures","regression-prevention","test-prioritization","root-cause-identification"],"summary_rewrite":"test-fixing identifies all failing tests, groups them by error type and root cause, then fixes them in priority order. It handles infrastructure issues first (imports, dependencies), then API changes, then logic bugs. After each fix group passes, it moves to the next until the full suite succeeds."},"files":[{"bytes":2965,"path":"engineering-workflow-plugin/skills/test-fixing/SKILL.md","sha256":"391f286dd828239fe6d82679204eaf4c850816e363000dc9ee99f1d5e253f108","url":"https://skillfed.io/files/mhattingpete/claude-skills-marketplace/test-fixing/3983717a/SKILL.md"}],"id":"mhattingpete/claude-skills-marketplace/test-fixing","links":{"html":"https://skillfed.io/mhattingpete/claude-skills-marketplace/test-fixing","md":"https://skillfed.io/mhattingpete/claude-skills-marketplace/test-fixing.md","repo":"https://github.com/mhattingpete/claude-skills-marketplace"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":91,"language":"HTML","last_updated":"2026-07-25","license":"Apache-2.0","name":"test-fixing","publisher":"mhattingpete","stars":657},"relations":{"similar":[{"id":"mhattingpete/claude-skills-marketplace/feature-planning"},{"id":"mhattingpete/claude-skills-marketplace/conversation-analyzer"},{"id":"mhattingpete/claude-skills-marketplace/code-refactor"},{"id":"mhattingpete/claude-skills-marketplace/code-auditor"},{"id":"mhattingpete/claude-skills-marketplace/review-implementing"},{"id":"mhattingpete/claude-skills-marketplace/code-transfer"},{"id":"mhattingpete/claude-skills-marketplace/project-bootstrapper"},{"id":"mhattingpete/claude-skills-marketplace/git-pushing"},{"id":"mhattingpete/claude-skills-marketplace/timeline-creator"},{"id":"mhattingpete/claude-skills-marketplace/dashboard-creator"}]},"slug":{"owner":"mhattingpete","repo":"claude-skills-marketplace","skill":"test-fixing"},"version":"3983717a"}