retry-fix

name	retry-fix
description	Investigate recurring bugs and regression cycles before attempting another fix. Use when: (1) User says 'still broken', 'X is blue again', 'this is the second/third/fourth time', 'we tried this before', 'I'm doing this many times', 'the regression is back', 'didn't stick', (2) A bug has been 'fixed' before but came back, (3) User mentions doing the same fix again, (4) Code changed for a feature but the previous fix got overwritten. ALWAYS use this skill before writing any code when a regression is detected — surface the prior-attempts table and get explicit confirmation before proceeding.
user-invocable	true
argument-hint	<problem-slug>

Retry Fix

A recurring bug has been patched before and regressed. This skill excavates all prior attempts, diagnoses the structural pattern that lets it regress, and gates any new code change behind explicit user confirmation.

Argument: $ARGUMENTS — a problem slug (e.g. active-frame-border, zoom-transform, modal-focus).

Step 1: Gather prior attempts

Run these searches in parallel. Use the slug and obvious keyword variants (kebab → spaces, camelCase, partial words):

# Git commits
git log --all --oneline -i --grep="<slug-keyword-1>"
git log --all --oneline -i --grep=  


gh issue list --state closed --search  -- 30