giuseppe-trisciuoglio/developer-kit

Comprehensive developer toolkit providing reusable skills for Java/Spring Boot, TypeScript/NestJS/React/Next.js, Python, PHP, AWS CloudFormation, AI/RAG, DevOps, and more.

Quality

90%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

This version of the tile failed moderation

Moderation pipeline encountered an internal error

description:: Recover from a broken state - diagnose issues, revert if needed, restore working state
argument-hint:: [issue-description]
allowed-tools:: Read, Write, Edit, Bash

Long-Running Agent - Recover from Broken State

Name: giuseppe-trisciuoglio/developer-kit
Rating: 90.85333333333334 (1 reviews)
Author: giuseppe-trisciuoglio

Use this command when the project is in a broken state and needs recovery.

Current Context

Git Status: !git status
Recent Commits: !git log --oneline -10

Recovery Protocol

Step 1: Diagnose the Problem

First, understand what's broken:

Check for syntax errors:
```
# For JS/TS projects
npm run lint 2>&1 | head -50

# For Java projects  
mvn compile 2>&1 | head -50

# For Python projects
python -m py_compile main.py
```

Check for failing tests:

npm test 2>&1 | tail -50
# or
mvn test 2>&1 | tail -50

Try to start the app:
```
# Check init script
cat .lra/init.sh
```
Check progress log for context:
```
tail -50 .lra/progress.txt
```

Step 2: Identify the Breaking Change

Look at git history to find when things broke:

# See recent changes
git log --oneline -10

# See what changed in last commit
git show --stat HEAD

# See diff of specific file
git diff HEAD~1 -- [problematic-file]

Step 3: Recovery Options

Choose the appropriate recovery strategy:

Option A: Quick Fix

If the issue is small and obvious:

Fix the specific issue
Test to confirm fix
Commit the fix
Update progress.txt with what happened

Option B: Revert Last Commit

If the last commit broke things:

# See what will be reverted
git show HEAD

# Revert (creates new commit)
git revert HEAD --no-edit

# Or soft reset to keep changes staged
git reset --soft HEAD~1

Option C: Revert to Known Good State

If multiple commits are problematic:

# Find last working commit
git log --oneline -20

# Reset to that commit (keeps changes)
git reset --soft [commit-hash]

# Or hard reset (discards changes)
git reset --hard [commit-hash]

Option D: Stash and Investigate

If you need to investigate without losing work:

git stash
# investigate...
git stash pop  # restore changes

Step 4: Verify Recovery

After applying a fix:

Run tests:
```
npm test
```
Start the app:
```
source .lra/init.sh
```
Verify core functionality:
- Can the app start?
- Do basic operations work?
- Are there any console errors?

Step 5: Document the Recovery

Update .lra/progress.txt:

---

### Recovery Session - [Date]

**Problem**: [What was broken]
**Cause**: [Why it broke]
**Solution**: [How it was fixed]
**Commits Reverted**: [If any]

**Lessons Learned**:
- [What to avoid in future]

---

Step 6: Update Feature Status

If a feature was incorrectly marked as passed:

# Use the mark-feature command
/developer-kit:devkit.lra.mark-feature [feature-id] failed [reason for failure]

Output

Provide a recovery report:

═══════════════════════════════════════════════════════════
                    RECOVERY COMPLETE
═══════════════════════════════════════════════════════════

🔍 Problem Identified
   Issue: TypeError in auth middleware
   Cause: Undefined variable after refactor
   Affected: F022 - User login flow

🔧 Recovery Action
   Strategy: Quick Fix
   Changes: Fixed undefined check in middleware
   Commit: def5678 - fix(auth): handle undefined user object

✅ Verification
   Tests: All passing (42/42)
   App: Starts successfully
   Core functionality: Working

📝 Updated Records
   - progress.txt: Recovery documented
   - F022 status: Remains passed (fix was minor)

💡 Recommendation
   Continue with normal workflow using /developer-kit:devkit.lra.start-session

═══════════════════════════════════════════════════════════