Skip to content
Development
Command

/devkit.lra.recover

Recover from a broken state - diagnose issues, revert if needed, restore working state

From plugin
developer-kit
36935 skills44 agents35 commands2 MCP
> /plugin marketplace add giuseppe-trisciuoglio/developer-kit
> /plugin install developer-kit@developer-kit

Command definition

devkit.lra.recover.md
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

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:

1. **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

2. **Check for failing tests**:

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

3. **Try to start the app**:

   # Check init script
   cat .lra/init.sh

4. **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: 1. Fix the specific issue 2. Test to confirm fix 3. Commit the fix 4. 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:

1. **Run tests**:

   npm test

2. **Start the app**:

   source .lra/init.sh

3. **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

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

Important

  • **DON'T PANIC**: Git history preserves everything
  • **ALWAYS test** after recovery
  • **DOCUMENT** what went wrong for future agents
  • **UPDATE** feature status if a "passed" feature was actually broken

Execution Instructions

**Agent Selection**: To execute this LRA task, use the following approach:

  • Primary: Use `general-purpose` agent with task management and state persistence capabilities
  • Or use `plan` agent for complex multi-step workflows
Read more
@giuseppe-trisciuoglio
Ships withdeveloper-kit

Modular plugin marketplace for Claude Code and agentic CLIs, with validated, spec-driven skills, agents, commands, and workflows for Java, TypeScript, Python, PHP, AWS, and AI.

369116 skills44 agents2 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
369
Star history of giuseppe-trisciuoglio/developer-kit on GitHub, a chart by star-history.com

Other commands on developer-kit.

More commands from other plugins.

build
Auto-invoked

build

Command

Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.

@addyosmani@addyosmaniInstall Command