
Create Forge Commands
Write new custom command files for the code-forge app, with lint, test and shell steps.
- Repository
- tailcallhq/forgecode
- Stars
- 7,638
- Licence
- Apache-2.0
- Files
- 1 file
What it does
This skill teaches an AI agent how to write custom commands for the code-forge coding tool. A command is a markdown file with a name, a description and a list of steps, saved in the project's .forge/commands folder so forge can find it. The agent learns the file format, naming rules, and special tags such as lint, test and shell that mark steps to run automatically.
Great for
- Developers who customise the code-forge tool with their own repeatable workflows
- Teams that want shared pre-commit or PR-description commands stored in their repository
- Anyone asking an agent to add, edit or understand code-forge command files
Skip it if
- People who do not use code-forge, since the commands only work in that application
- Using it blindly in a repo with unreviewed tags, because <lint>, <test> and <shell> tags cause the listed shell commands to be run on your machine
Try asking
- “Create a command called pr-description that updates the PR title and body using the GH CLI”
- “Write a check command that runs lint and test and fixes any issues found”
- “Add a command to .forge/commands that cleans build output before a release”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 1 original files, the Apache-2.0 licence and an attribution note.
create-command.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip create-command.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip create-command.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Review every <shell>, <lint> and <test> tag before running a command you did not write, since these execute on your machine
- Keep command names verb-based and hyphenated, for example run-tests rather than RunTests
- Put command files only in <cwd>/.forge/commands or forge will not load them
What's inside
- SKILL.md
Redistributed unmodified from tailcallhq/forgecode under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.