Debug Cli

What it does

This skill provides a structured workflow for debugging and verifying changes to the forge CLI application. It focuses on systematic error analysis, using specific commands and flags to test functionality and reproduce issues. The core principle is to ensure changes are thoroughly tested in debug mode before any potential commitment.

When to use it

• When developing or modifying the forge CLI application.
• To systematically troubleshoot reported bugs within the forge CLI.
• For testing new features added to the forge CLI.
• When reproducing user-reported conversation issues with the CLI.
• To verify fixes for identified bugs in a controlled environment.

Key capabilities

• Build in Debug Mode: Uses cargo build for faster debugging cycles (avoiding --release).
• Help Documentation Access: Provides commands to view current command and option documentation using --help.
• Testing with -p Flag: Allows running forge with tasks in non-interactive mode.
• Conversation Dumps: Exports conversations as JSON or HTML files for detailed analysis and reproduction.
• Conversation Cloning: Enables creating copies of existing conversations to prevent modification of original bug evidence during debugging.

Example prompts

These are not user prompts to the skill, but example commands used with the skill:

• ./target/debug/forge --help (To view main help documentation)
• ./target/debug/forge -p "create a hello world rust program" (To test with a simple prompt)
• ./target/debug/forge conversation dump <conversation-id> (To export a conversation as JSON)

Tips & gotchas

• Always build in debug mode: Use cargo build, not cargo build --release.
• Clone conversations before modifying: Never directly modify original conversations when debugging.
• Understand the workflow: Follow the prescribed steps (build, documentation, testing, debugging) for effective troubleshooting.