debug-command-storage

Captures failing commands and generates timestamped executable scripts for replay and debugging.

2|2|Updated Aug 4, 2020
One-click install
npx skills add https://github.com/hotvect/hotvect --skill debug-command-storage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-command-storage
Source: https://github.com/hotvect/hotvect/tree/main/hotvect-claude-code-plugin/skills/debug-command-storage
Command: npx skills add https://github.com/hotvect/hotvect --skill debug-command-storage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Store failing command invocations for reproducible debugging and incident analysis of hotvect operations.

Core Features & Use Cases

  • Captures the full failing command with all arguments
  • Converts relative paths to absolute paths for reliable replay
  • Writes timestamped, executable shell scripts in the working directory
  • Avoids modifying user configuration files to preserve safety and privacy

Quick Start

Execute this skill immediately after a failure to generate a timestamped shell script that replays the command.

Frequently Asked Questions about debug-command-storage

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

FAQPage Schema
How do I capture a failed shell command for reproducible debugging?

To capture a failed shell command for reproducible debugging, this skill records the full invocation, converts relative paths to absolute paths, and saves it as a timestamped executable script in your working directory.

What is the best way to record failing Java-based command invocations for incident analysis?

Recording failing Java-based command invocations for incident analysis is done by capturing the exact command line and substituting algorithm definitions with names where possible. This generates timestamped replay scripts without altering user configurations.

Does command storage modify my existing shell configuration files?

Command storage does not modify your existing shell configuration files. It safely preserves your environment by writing timestamped replay scripts directly into the current working directory instead of altering system or user settings.

How do I replay a failed hotvect command with absolute paths?

To replay a failed hotvect command with absolute paths, run this skill immediately after the failure. It generates an executable shell script in the current directory that automatically uses absolute paths and substitutes algorithm definitions with names.

Can I use this command capture tool with hv and hv-ext operations?

You can use this command capture tool with hv, hv-ext, and Java-based commands. It records the full failing invocation across these environments and converts relative paths to absolute paths for reliable replay during debugging.