debug-cli skillA
debug-cli is agent-read markdown (skill) from tailcallhq/forgecode: 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..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# CLI Debug Skill This skill provides a systematic workflow for debugging and verifying changes to the forge CLI application. ## Core Principles 1. **Always get latest docs first**: Run `--help` to see current commands and options 2. **Use `-p` for testing**: Test forge by giving it tasks with the `-p` flag 3. **Never commit**: This is for debugging only - don't commit changes 4. **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: ```bash 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: ```bash # 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 ``` ### 3. Test with `-p` Flag Use the `-p` flag to give forge a task to complete without interactive mode: ```bash # Test with a simple prompt …
Read the whole file at its exact version.
How to install
mdr add tailcallhq/forgecode/debug-cli@git:20251129.d8cba1fmdr add tailcallhq/forgecode/debug-cli@sha256:5a67fb126d8cfd64Pin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_wxlb3oorbsjdvbly)
2 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20251129.d8cba1f latest | 2025-11-29 | d8cba1f | 6,542 B | A | view · diff |
| git:20251124.2b8f212 | 2025-11-24 | 2b8f212 | 6,588 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6542 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tailcallhq/forgecode · 7,637 stars · license Apache-2.0 · pushed 2026-09-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wxlb3oorbsjdvbly GET https://markdownregistry.com/api/v1/resolve?ref=tailcallhq/forgecode/debug-cli GET https://markdownregistry.com/api/v1/blob/5a67fb126d8cfd6445468b20fad7ec98ff18b1b4d8503d3af1958e670d3fed6a
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.