skills.rest
AngelP17
AngelP17COMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug-cli

Debug and validate Forge CLI behavior using cargo builds and shell commands.

1|Updated Jan 29, 2026
Search Tags:#workflow#testing#debugging#cli#cargo#forge
One-click install
npx skills add https://github.com/AngelP17/factoryops-console --skill debug-cli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-cli
Source: https://github.com/AngelP17/factoryops-console/tree/main/factoryops-console/.agent/skills/debug-cli
Command: npx skills add https://github.com/AngelP17/factoryops-console --skill debug-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Forge CLI can become difficult to debug and extend as features evolve. This skill provides a repeatable workflow to diagnose command behavior, verify argument parsing, and test changes without introducing instability.

Core Features & Use Cases

  • Structured debugging workflow: step-by-step procedures to reproduce CLI issues, inspect help output, and validate behavior.
  • Safe testing and verification: uses -p tasks to simulate real-world commands and confirms results without committing changes.
  • CLI extension and maintenance: guides adding new commands or options and troubleshooting CLI-related issues in a repeatable way.

Quick Start

  • Build in debug mode: cargo build
  • Inspect help and command-specific help: ./target/debug/forge --help and ./target/debug/forge [COMMAND] --help
  • Run a non-interactive task to verify behavior: ./target/debug/forge -p "describe the current CLI structure"

Frequently Asked Questions about debug-cli

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

FAQPage Schema
How do I debug Forge CLI command behavior and test changes locally?▼

Debug Forge CLI by building in debug mode with cargo build, then inspect help output and test commands using ./target/debug/forge --help and ./target/debug/forge [COMMAND] --help. Run non-interactive tasks with -p flags to verify behavior safely without committing changes.

What's the best way to reproduce and diagnose CLI issues in a workflow?▼

Use a structured debugging workflow to reproduce CLI issues step-by-step, inspect help output, and validate argument parsing. This repeatable approach diagnoses command behavior and confirms results before implementing fixes or extensions.

Can I test new CLI commands or options without introducing instability?▼

Yes. The workflow uses cargo to build locally and -p task simulation to test changes in isolation. This safe verification method lets you add new commands or troubleshoot CLI-related issues repeatedly before deployment.

Do I need Rust and cargo to debug the Forge CLI?▼

Yes. Debugging and testing the Forge CLI requires a Rust toolchain with cargo to build locally and standard shell commands for verification of command behavior and argument parsing.

How do I validate CLI behavior across different use cases?▼

Build in debug mode, inspect command-specific help, and run non-interactive -p tasks that simulate real-world commands. This structured approach confirms CLI behavior across typical use cases without committing experimental changes.

Related Skills

Explore More Software Engineering Skills→
jyasuujyasuu

rust

Manage Rust toolchains and automate cargo build, test, and cross-compile workflows.

Community
Intermediate
picmakpropicmakpro
9

debugger

Diagnose root causes of bugs and document verified fixes.

Community
Advanced
krzemienskikrzemienski
2

rust-cli-validation

Execute cargo check, clippy, and build with runtime tests for Rust CLI binaries.

Community
Advanced
shushuznshushuzn
4

rairos-dev

Build, test, and debug the Rairos Rust codebase with cargo and Makefile workflows.

Community
Intermediate