skills.rest
TalonT-Org
TalonT-OrgOFFICIAL
Explore all skills by this author →
GitHub

resolve-failures

Apply targeted code fixes to failing test suites in a Git worktree.

5|1|Updated Feb 18, 2026
Search Tags:#code quality#automation#git#testing#ci/cd#debugging
One-click install
npx skills add https://github.com/TalonT-Org/AutoSkillit --skill resolve-failures
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolve-failures
Source: https://github.com/TalonT-Org/AutoSkillit/tree/main/src/autoskillit/skills/resolve-failures
Command: npx skills add https://github.com/TalonT-Org/AutoSkillit --skill resolve-failures

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automatically fixes failing tests in a worktree, ensuring code stability before merging and preventing broken builds.

Core Features & Use Cases

  • Automated Test Remediation: Identifies and fixes test failures based on implementation plans.
  • Iterative Fixing: Attempts up to three rounds of fixes and re-tests to resolve issues.
  • Use Case: After implementing a new feature, if tests fail, this Skill will attempt to correct the issues without merging, leaving the worktree ready for a final review.

Quick Start

Use the resolve-failures skill to fix test failures in the worktree located at './my-feature-worktree', using the plan file './plans/feature-plan.md', against the 'main' branch.

Frequently Asked Questions about resolve-failures

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix failing tests in a Git worktree without merging broken code?▼

Failing tests in a Git worktree can be fixed by applying targeted code fixes based on an implementation plan, iteratively testing and committing changes to ensure a green build state without merging.

Can I automate test remediation against the main branch using an implementation plan?▼

Yes, automated test remediation applies targeted code fixes from a provided implementation plan file, iteratively testing and committing changes against the main branch to resolve failures.

What is the best way to iteratively debug failing test suites before a Git merge?▼

The best way to iteratively debug failing test suites is running up to three rounds of automated fixes and re-tests within a Git worktree, leaving the branch ready for review without merging.

Does automated test fixing work without merging changes into the main branch?▼

Yes, automated test fixing works by validating the worktree and executing tests without merging, ensuring code stability and leaving the worktree ready for final review.

Why do I need a plan file for automated test remediation in a worktree?▼

A plan file is required for automated test remediation to provide the targeted implementation logic needed to apply code fixes, handle worktree validation, and resolve failing tests.

What are the limitations of iterative test fixing for CI/CD pipelines?▼

A limitation of iterative test fixing is that it attempts a maximum of three rounds of fixes and does not merge changes, requiring manual review and integration into CI/CD pipelines after achieving a green build.

Related Skills

Explore More Software Engineering Skills→
f4irlinef4irline
5

git-worktree-find

Resolve a git branch's worktree path or create one via git-worktree-prepare.

Community
Intermediate
cwijayasundaracwijayasundara
3

gate

Execute pre-merge quality gate checks with automated code reviews and security checks.

Community
Advanced
AnveioAnveio
1

task-pull-request

Automate GitHub pull request creation, reviews, feedback, and merges via gh CLI.

Community
Intermediate
wahidyankfwahidyankf
3

monitor-ci

Monitor Nx Cloud CI Attempts and apply self-healing fixes.

Community
Advanced