batch-retry

Clean up failed batch task branches and PRs, then re-execute tasks.

40|22|Updated Jan 28, 2024
One-click install
npx skills add https://github.com/vultisig/vultisig-ios --skill batch-retry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: batch-retry
Source: https://github.com/vultisig/vultisig-ios/tree/main/.claude/skills/batch-retry
Command: npx skills add https://github.com/vultisig/vultisig-ios --skill batch-retry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates retrying failed batch tasks by cleaning up partial work and re-running with the same parameters.

Core Features & Use Cases

  • Identify failed tasks from a batch run and locate associated branches and PRs
  • Clean up failed attempts by closing PRs and deleting branches (and local copies) safely
  • Re-execute tasks using a consistent agent configuration and PRD context
  • Generate a summary report of results for each retried task

Quick Start

Run /batch-retry with the batch indices of the failed tasks to initiate a clean re-run

Frequently Asked Questions about batch-retry

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

FAQPage Schema
How do I retry failed batch tasks and clean up leftover branches and PRs?

To retry failed batch tasks, the batch-retry process identifies failed runs, closes associated PRs, deletes leftover branches, and re-executes the tasks with the same parameters.

What is the best way to automate re-running failed CI/CD batch tasks safely?

Automating failed CI/CD batch task retries safely involves cleaning up partial work from prior attempts, including local branch copies, before re-executing with the original agent configuration.

Can I re-execute batch automation tasks using the same PRD context after a failure?

Yes, batch tasks can be re-executed using a consistent agent configuration and the original PRD context, ensuring the retried tasks operate under the same parameters as the initial run.

Does batch retrying work with existing git workflows that spawn branches for each task?

Yes, batch retrying integrates with git workflows by identifying task-specific branches and PRs spawned during the batch run, safely closing and deleting them before initiating a clean re-run.

How do I get a summary report of retried batch automation tasks?

After re-executing failed batch tasks, the process generates a summary report of results for each retried task, providing standardized tracking of the retry outcomes.