autorun-maintainer

Diagnose and deploy autorun hook systems for Claude Code and Gemini CLI.

12|2|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/ahundt/autorun --skill autorun-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autorun-maintainer
Source: https://github.com/ahundt/autorun/tree/main/plugins/autorun/skills/autorun-maintainer
Command: npx skills add https://github.com/ahundt/autorun --skill autorun-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill addresses complex issues with the autorun hook system, ensuring its stability, proper deployment, and effective debugging of "invisible failures" or "zombie states" where code changes aren't reflected.

Core Features & Use Cases

  • Deep Debugging: Provides a systematic hierarchy for diagnosing hook errors, from plumbing to source code checks.
  • Platform Specifics: Details schema requirements and error handling nuances for both Claude Code and Gemini CLI.
  • Deployment & Sync: Guides users through correct installation, synchronization, and restart procedures to avoid stale code.
  • Use Case: When autorun --restart-daemon doesn't fix hook errors, or when rm commands are unexpectedly allowed, this Skill provides the diagnostic steps to pinpoint and resolve the root cause.

Quick Start

Use the autorun-maintainer skill to diagnose why the autorun daemon is not responding after a code update.

Frequently Asked Questions about autorun-maintainer

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

FAQPage Schema
How do I debug autorun hooks when code changes aren't reflected in Claude Code?

Debug autorun hook invisible failures by following a diagnostic hierarchy that checks plumbing, deployment synchronization, and source code state to resolve stale code execution. This process inspects hook errors and zombie states where updates fail to apply.

Why does the autorun daemon still error after running --restart-daemon?

When autorun --restart-daemon doesn't fix hook errors, stale code or deployment sync issues are likely the root cause. You must verify correct installation procedures and check the platform-specific schema requirements for Claude Code or Gemini CLI.

How do I deploy autorun hooks correctly for Gemini CLI?

Deploy autorun hooks for Gemini CLI by following platform-specific schema requirements and synchronization procedures. Correct installation avoids zombie states and ensures the hook system accurately reflects code updates without reverting.

What causes safety guards to become inactive and allow rm commands in autorun?

Safety guard inactivity allowing unexpected rm commands usually stems from code reversion or deployment failures. Diagnose the autorun hook system by checking the source code state and verifying deployment stability.

Does the autorun hook system work with both Claude Code and Gemini CLI?

The autorun hook system supports both Claude Code and Gemini CLI, providing platform-specific schemas and error handling nuances. It addresses deployment strategies and stability insights tailored to each platform's requirements.