create-command skillA
create-command is agent-read markdown (skill) from tailcallhq/forgecode: Create new commands for the code-forge application. Commands are stored as .md files in the <cwd>/.forge/commands directory with YAML frontmatter (name, description) and markdown body containing command steps. Use when users need to add new commands, modify existing commands, or understand the command file structure. Supports special command tags like <lint> and <test> for automated workflows..
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
# Create Commands
Create and manage commands for the code-forge application. Commands are modular workflows that can be invoked to perform specific tasks.
## File Location
**CRITICAL**: All command files must be created in the `<cwd>/.forge/commands` directory, where `<cwd>` is the current working directory of your code-forge project.
- **Directory**: `<cwd>/.forge/commands`
- **File format**: `{command-name}.md`
- **Example**: If your project is at `/home/user/my-project`, commands go in `/home/user/my-project/.forge/commands/`
This is the only location where forge will discover and load custom commands.
## Command File Structure
Every command file must have:
1. **YAML Frontmatter** (required):
- `name`: Command identifier (use hyphens for multi-word names)
- `description`: What the command does
2. **Command Body** (required):
- List of steps to execute
- Special tags for automated workflows
- Clear instructions for each step
### Example Command File
```markdown
---
name: check
description: Checks if the code is ready to be committed
---
- Run the `lint` and `test` commands and verify if everything is fine.
…Read the whole file at its exact version.
How to install
mdr add tailcallhq/forgecode/create-command@git:20260126.0427bf8mdr add tailcallhq/forgecode/create-command@sha256:18e7e101b3a8ef47Pin 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_oxgnqt3ge3bebm45)
2 badge views in 30 days
Versions
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 (15714 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_oxgnqt3ge3bebm45 GET https://markdownregistry.com/api/v1/resolve?ref=tailcallhq/forgecode/create-command GET https://markdownregistry.com/api/v1/blob/18e7e101b3a8ef47c1ff9a96e4b9a2db5fac7e297bd6b12c361c304a3ed32d19
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.
More from tailcallhq/forgecode
Every file in tailcallhq/forgecode