debug-cli

Build and test the Forge CLI in debug mode to reproduce bugs.

7.5k|1.4k|Updated Dec 8, 2024
One-click install
npx skills add https://github.com/tailcallhq/forgecode --skill debug-cli-tailcallhq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-cli
Source: https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/debug-cli
Command: npx skills add https://github.com/tailcallhq/forgecode --skill debug-cli-tailcallhq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a structured workflow to debug, modify, and extend the Forge CLI, enabling developers to reproduce issues, validate fixes, and verify CLI behavior across environments.

Core Features & Use Cases

  • Build the application in debug mode to iterate quickly during development.
  • Inspect help and command options with targeted tests using the -p flag to simulate real tasks.
  • Debug and reproduce CLI bugs using conversation dumps and cloning workflows, then apply fixes without affecting production builds.
  • Integrate into a developer workflow to accelerate CLI enhancements, bug fixes, and validation across different environments.

Quick Start

Build the Forge CLI in debug mode, then run the help command and a sample task with -p to verify the workflow.

Frequently Asked Questions about debug-cli

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

FAQPage Schema
How do I debug and reproduce a bug in a CLI application?

To debug CLI behavior, build the application in debug mode, run targeted tests with the -p flag to simulate real tasks, and use conversation dumps to reproduce and analyze bugs.

What is the best way to extend and test CLI commands safely?

The best way to extend CLI commands safely is to use a reproducible workflow that applies targeted tests and enforces non-destructive verification, ensuring fixes do not affect production builds.

Can I simulate real tasks when testing CLI behavior in debug mode?

Yes, you can simulate real tasks when testing CLI behavior by running a sample task with the -p flag after building the application in debug mode to validate the workflow.

Does debugging a CLI in debug mode affect my production builds?

No, debugging a CLI in debug mode does not affect production builds, because the workflow enforces safe, non-destructive verification to isolate bug reproduction and applied fixes.

Why do I need conversation dumps when debugging CLI issues?

You need conversation dumps when debugging CLI issues to inspect exact command interactions, allowing you to accurately reproduce bugs and validate applied fixes across different environments.