repo-rescue

Automate a five-phase workflow to diagnose and fix broken repositories.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/robwestz/memoryporter --skill repo-rescue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-rescue
Source: https://github.com/robwestz/memoryporter/tree/main/knowledge/meta-skills/repo-rescue
Command: npx skills add https://github.com/robwestz/memoryporter --skill repo-rescue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, file-read, file-write, glob, grep, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill tackles the challenge of diagnosing and fixing broken or abandoned repositories by automating a structured workflow.

Core Features & Use Cases

  • Five-Phase Workflow: Automates the discovery, diagnosis, planning, fix, and reporting phases.
  • Automated Fixes: Applies quick win and day 1 fixes with build verification.
  • Security Checks: Detects hardcoded secrets, insecure configurations, and common vulnerabilities.
  • Use Case: When faced with a repository that is failing to build or is stuck in a broken state, this Skill can automatically identify issues and suggest fixes.

Quick Start

Use the repo-rescue skill by running the command: "rescue this repo" or "the build is broken, triage it".

Frequently Asked Questions about repo-rescue

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

FAQPage Schema
How do I triage a broken repository that is failing to build?

To triage a broken repository failing to build, you can automate the process using a five-phase workflow that handles discovery, diagnosis, planning, fixing, and reporting. This approach scans for missing dependencies and configuration issues to identify and apply required fixes.

What is the best way to rescue an abandoned codebase with missing dependencies?

The best way to rescue an abandoned codebase with missing dependencies is to run an automated triage workflow. It diagnoses the repository, suggests quick win fixes, and verifies the build to restore the project to a functional state.

Can I detect hardcoded secrets and security vulnerabilities during codebase repair?

Yes, you can detect hardcoded secrets and security vulnerabilities during codebase repair. The triage workflow includes a dedicated diagnosis phase that scans for insecure configurations and common vulnerabilities alongside standard build errors.

Do I need local repository access and build tools to run an automated repo triage?

Yes, you need local repository access and the appropriate build tools for the target language to run an automated repo triage. The workflow applies fixes and verifies them by executing builds locally.

What steps are involved in an automated repository rescue workflow?

An automated repository rescue workflow involves five sequential steps: discovery, diagnosis, planning, fixing, and reporting. It scans for issues, applies quick win fixes, verifies the build, and generates a final report on the codebase status.

Why does codebase repair fail when applying automated fixes to stuck repositories?

Codebase repair might fail if the local environment lacks the appropriate build tools for the target language or if local repository access is restricted. The workflow requires these dependencies to successfully apply fixes and verify the build.