Use when users need to debug, modify, or extend the code-forge application's CLI commands, argument parsing, or CLI behavior. This includes adding new commands, fixing CLI bugs, updating command options, or troubleshooting CLI-related issues.
SkillScore82Maintained
Automatic
◆Coding pack
Last verified 8/21/2026
What it changes
Passed 18 of 22 test cases with the skill, and 6 of 22 without it.
Without skill27%
With skill82%
Checks it passed that the model alone missed
Compiles using cargo build.
Executes the test prompt using the -p flag.
Checks CLI help using ./target/debug/forge --help.
and 14 more in the full report
12 fixed6 passed either way4 still failing0 broke
Pass-rate lift
+55 pp
Tokens
+50%
Agent turns
0%
Response time
-61%
Model gemini-3.6-flashMeasured 8/21/2026v118 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 12
Prompt
I need to trace internal execution steps and detailed logging while running a test prompt in forge CLI. Which CLI parameter flag enables verbose diagnostic output?
What was checked, without and with the skill
Checked
Without skill
With skill
Applies the --verbose flag when executing ./target/debug/forge.
Missed
Passed
case-11 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md206 linessingle file
CLI Debug Skill
This skill provides a systematic workflow for debugging and verifying changes to the forge CLI application.
Core Principles
Always get latest docs first: Run --help to see current commands and options
Use -p for testing: Test forge by giving it tasks with the -p flag
Never commit: This is for debugging only - don't commit changes
Clone conversations: When debugging conversation bugs, clone the source conversation before reproducing
Workflow
1. Build the Application
Always build in debug mode after making changes:
cargo build
Never use cargo build --release for debugging - it's significantly slower and unnecessary for verification.
2. Get Latest Documentation
Always start by checking the latest help to understand current commands and options:
# Main help - do this first
./target/debug/forge --help
# Command-specific help
./target/debug/forge [COMMAND] --help
# Subcommand help
./target/debug/forge [COMMAND] [SUBCOMMAND] --help