Neat-Freak Knowledge Closeout
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
Creates and structures custom command files for the code-forge CLI, with YAML frontmatter plus special tags for automated lint and test steps.
$ npx skills add tailcallhq/forgecode --skill create-command -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tailcallhq/forgecode create-command --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.forge/skills/create-command .claude/skills/create-command && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "create-command" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/create-command into .claude/skills/create-command/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-command", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/create-commandType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tailcallhq/forgecode --skill create-command -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tailcallhq/forgecode create-command --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.forge/skills/create-command .agents/skills/create-command && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "create-command" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/create-command into .agents/skills/create-command/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-command", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tailcallhq/forgecode --skill create-command -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tailcallhq/forgecode create-command --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.forge/skills/create-command .cursor/skills/create-command && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "create-command" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/create-command into .cursor/skills/create-command/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-command", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tailcallhq/forgecode.git --path .forge/skills/create-command--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tailcallhq/forgecode --skill create-command -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tailcallhq/forgecode create-command --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.forge/skills/create-command .gemini/skills/create-command && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "create-command" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/create-command into .gemini/skills/create-command/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-command", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tailcallhq/forgecode create-commandInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tailcallhq/forgecode --skill create-command -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .github/skills && cp -r skills-src/.forge/skills/create-command .github/skills/create-command && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "create-command" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/create-command into .github/skills/create-command/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-command", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tailcallhq/forgecode --skill create-command -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tailcallhq/forgecode create-command --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.forge/skills/create-command .opencode/skills/create-command && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "create-command" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/create-command into .opencode/skills/create-command/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-command", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
create-commandCreates and structures custom command files for the code-forge CLI, with YAML frontmatter plus special tags for automated lint and test steps.
Every command is a single Markdown file placed under the project's forge commands directory, named after the command, and it is the only location forge discovers custom commands from. Each file needs YAML frontmatter with a name and description, plus a body listing the steps to execute in order, written as clear, specific, actionable instructions starting with an action verb.
Command names use hyphens for multi-word names and should read as verbs, such as check or run-tests, rather than nouns like checker. Special tags mark steps meant for automated linting or testing inside the command body, letting one command mix plain instructions with these automated steps.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 92a5699. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown, bash and yaml).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Code-Forge Command Creator loads about 3.9k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 1,112 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from tailcallhq/forgecode at commit 92a5699, republished under its Apache-2.0 licence (© tailcallhq). 1,112 words, ~3,929 tokens.
.claude/skills/create-command/SKILL.md (or your agent's skills folder).Create and manage commands for the code-forge application. Commands are modular workflows that can be invoked to perform specific tasks.
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.
<cwd>/.forge/commands{command-name}.md/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.
Every command file must have:
YAML Frontmatter (required):
name: Command identifier (use hyphens for multi-word names)description: What the command doesCommand Body (required):
---
name: check
description: Checks if the code is ready to be committed
---
- Run the `lint` and `test` commands and verify if everything is fine.
<lint>cargo +nightly fmt --all; cargo +nightly clippy --fix --allow-staged --allow-dirty --workspace</lint>
<test>cargo insta test --accept --unreferenced=delete</test>
- Fix every issue found in the processThis sample demonstrates all three tag types:
---
name: sample-command
description: Sample command demonstrating the command file structure
---
This is a sample command that demonstrates the structure of command files.
- First step: Perform an initial action
<lint>echo "Running linting..."</lint>
- Second step: Execute tests
<test>echo "Running tests..."</test>
- Third step: Complete the workflow
<shell>echo "Workflow complete!"</shell>
- Final step: Verify everything worked correctlyIdentify what the command should accomplish:
Use verb-based names with hyphens for multi-word commands:
check, fixme, pr-description, run-testschecker, fixing, PRdescriptionCreate the file in the <cwd>/.forge/commands directory with the format: {command-name}.md
IMPORTANT: The file MUST be in <cwd>/.forge/commands where <cwd> is your current working directory. Commands placed anywhere else will not be discovered by forge.
---
name: your-command-name
description: Clear, concise description of what this command does
---Use markdown lists for steps. Each step should:
Use these tags for automated workflows:
<lint> TagFor linting/formatting commands:
<lint>cargo +nightly fmt --all; cargo +nightly clippy --fix --allow-staged --allow-dirty --workspace</lint><test> TagFor testing commands:
<test>cargo insta test --accept --unreferenced=delete</test><shell> TagFor general shell commands (not linting or testing):
<shell>rm -rf target/debug</shell>Tags should be placed on their own line after the step description:
- Run linting and testing
<lint>your-lint-command</lint>
<test>your-test-command</test>Single-step or instruction-only commands:
---
name: fixme
description: Looks for all the fixme comments in the code and attempts to fix them
---
Find all the FIXME comments in source-code files and attempt to fix them.Commands with multiple sequential steps:
---
name: pr-description
description: Updates the description of the PR
---
- I have created a Pull Request with all the accepted changes
- Understand the current PR deeply using the GH CLI and update the PR title and description
- Make sure the title follows conventional commits standard
- Top-level summary should contain 2-3 lines about the core functionality improvementsCommands that include automated checks:
---
name: check
description: Checks if the code is ready to be committed
---
- Run the `lint` and `test` commands and verify if everything is fine.
<lint>cargo +nightly fmt --all; cargo +nightly clippy --fix --allow-staged --allow-dirty --workspace</lint>
<test>cargo insta test --accept --unreferenced=delete</test>
- Fix every issue found in the process---
name: simple-command
description: Does one specific thing
---
Single clear instruction or description.---
name: automated-workflow
description: Runs automated checks and performs follow-up actions
---
- Run automated checks
<lint>your-lint-command</lint>
<test>your-test-command</test>
- Review and fix any issues found
- Complete the workflow---
name: multi-step-workflow
description: Performs multiple sequential steps
---
- First step with clear action
- Second step with context
- Third step with specific requirements
- Final step with verification---
name: git-workflow
description: Performs git operations
---
- Stage changes
<shell>git add .</shell>
- Run pre-commit checks
<lint>cargo fmt --all</lint>
<test>cargo test</test>
- Commit with message
<shell>git commit -m "your commit message"</shell>
- Push to remote
<shell>git push</shell><lint>, <test>, and <shell> tags---
name: commit-check
description: Verifies code is ready to commit
---
- Run linting and tests
<lint>cargo fmt --all; cargo clippy --fix --allow-staged</lint>
<test>cargo test</test>
- Review and fix any issues
- Stage all changes---
name: update-docs
description: Updates documentation for recent changes
---
- Review recent code changes
- Identify functions or modules that need documentation
- Update inline documentation comments
- Regenerate any auto-generated docs
- Verify documentation builds successfully---
name: cleanup
description: Cleans up temporary files and artifacts
---
- Remove build artifacts
<shell>rm -rf target/debug</shell>
- Remove temporary files
<shell>find . -name "*.tmp" -delete</shell>
- Clean up dependency caches if needed
- Verify the project still builds---
name: build-deploy
description: Builds the project and deploys to staging
---
- Build the project in release mode
<shell>cargo build --release</shell>
- Run integration tests
<test>cargo test --test integration</test>
- Build Docker image
<shell>docker build -t myapp:latest .</shell>
- Tag image for staging
<shell>docker tag myapp:latest myapp:staging</shell>
- Push to registry
<shell>docker push myapp:staging</shell>
- Deploy to staging environment
<shell>kubectl set image deployment/myapp myapp=myapp:staging</shell>Use this checklist to verify your command is complete and correct:
<cwd>/.forge/commands directory (CRITICAL)check.md for name: check).md extension--- delimitersname field is presentname uses lowercase lettersname uses hyphens for multi-word namesname is verb-based (imperative form)description field is presentdescription is clear and concisedescription describes what, not how-)<lint>, <test>, <shell>)forge list command --custom (or forge list cmd) and verify your command appears in the listBad: Wrong delimiter:
---
name: my-command
description: My command(Missing closing ---)
Good: Correct:
---
name: my-command
description: My command
---Bad: Missing required field:
---
name: my-command
---(Missing description)
Good: Correct:
---
name: my-command
description: Does something useful
---Bad: CamelCase name:
---
name: myCommand
description: Does something
---Good: Correct:
---
name: my-command
description: Does something
---Bad: Noun instead of verb:
---
name: checker
description: Checks something
---Good: Correct:
---
name: check
description: Checks something
---Bad: No action verb:
---
name: test
description: Runs tests
---
- The tests
- The codeGood: Correct:
---
name: test
description: Runs tests
---
- Run all tests
- Verify code qualityBad: Vague steps:
---
name: deploy
description: Deploys application
---
- Do the deployment
- Make sure it worksGood: Correct:
---
name: deploy
description: Deploys application to production
---
- Build the Docker image
<shell>docker build -t myapp:latest .</shell>
- Push to registry
<shell>docker push myapp:latest</shell>
- Deploy to production
<shell>kubectl set image deployment/myapp myapp=myapp:latest</shell>
- Verify deployment is healthyBad: Tag on same line:
- Run tests <test>cargo test</test>Good: Correct:
- Run tests
<test>cargo test</test>Bad: Invalid tag:
- Run checks
<check>cargo clippy</check>Good: Correct:
- Run checks
<lint>cargo clippy</lint>Bad: Incomplete command:
- Format code
<lint>cargo fmt</lint>(Missing --all flag)
Good: Correct:
- Format code
<lint>cargo fmt --all</lint><cwd>/.forge/commands (where <cwd> is current working directory){command-name}.md<lint> - For linting/formatting commands<test> - For testing commands<shell> - For general shell commands<lint> when running formatters or linters<test> when running test suites<shell> for other shell commandsAfter creating a command, test it by:
Syntax Check: Verify YAML is valid
# If you have yamllint installed
yamllint path/to/your-command.mdManual Review: Read through the command
Execution Test: Run the command
Forge Recognition Test: Verify the command is recognized by forge
# Option 1: List all commands (custom commands marked as type: custom)
forge list command
# Option 2: List only custom commands
forge list cmd
# Option 3: List only custom commands (newer versions)
forge list command --customEdge Cases: Consider unusual scenarios
After creating a command:
Verify the file location: Ensure the file is in <cwd>/.forge/commands directory (CRITICAL - commands anywhere else will not be found)
Check YAML frontmatter is valid (use --- delimiters)
Ensure the command name matches the filename (without .md)
Verify the command is recognized by forge:
# Option 1: List all commands (custom commands marked as type: custom)
forge list command
# Option 2: List only custom commands
forge list cmd
# Option 3: List only custom commands (newer versions)
forge list command --customYour new command should appear in the list with its name and description
Test the command to ensure it works as expected
Verify special tags are properly formatted
If your command doesn't appear in the list, check:
<cwd>/.forge/commands directory (this is the most common issue)name field in frontmatter--- delimitersname and description fields are presentIf you're unsure about something:
© tailcallhq, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .forge/skills/create-command of tailcallhq/forgecode.
Open the folder on GitHubat commit 92a5699
Code-Forge Command Creator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Code-Forge Command Creator this skilltailcallhq/forgecode | 7.6k | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills | 21k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Dsh Web Documentationzhu1090093659/dsh-web | 8.4k | — | ~479 | Automated safety check: Pass | Apache-2.0 | |
| Harness Engineering GuideOdradekAI/harness-engineering-guide | 125 | 1 repos | ~4.3k | Automated safety check: Pass | Apache-2.0 | |
| Agent Setup Health Audittw93/Waza | 7.2k | — | ~5.2k | Automated safety check: Notes | MIT | |
| Agnixagent-sh/agnix | 444 | — | ~874 | Automated safety check: Pass | Apache-2.0 |
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
zhu1090093659/dsh-web
A skill your agent uses when adding or editing dsh-web README files, docs, AGENTS.md instructions, user-facing configuration text, or bilingual documentation pairs.
OdradekAI/harness-engineering-guide
Audit, design, and implement AI agent harnesses for any codebase.
tw93/Waza
Audits a project's agent configuration, instruction drift, hooks, MCP and AI maintainability, then reports prioritized findings with evidence and next actions.
agent-sh/agnix
A skill your agent uses when user asks to 'lint agent configs', 'validate skills', 'check CLAUDE.md', 'validate hooks', 'lint MCP'.
ywwynm/EverythingDone
Sets up an Agent skills block in AGENTS.md/CLAUDE.md and docs/agents/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…
tailcallhq/forgecode
Resolves Git merge conflicts with a plan-first workflow that keeps both sides' intent, regenerates lock files and backs up deleted-but-modified files.
tailcallhq/forgecode
Gives a systematic process for debugging the forge CLI: build in debug mode, check the latest help output, test with the non-interactive -p flag, and clone conversations before reproducing bugs.
tailcallhq/forgecode
Finds every FIXME comment in a codebase, groups related ones across files into one task, implements the work they describe and removes the comments once it is done.
tailcallhq/forgecode
Checks that ReasoningConfig fields are serialized into the right provider-specific JSON for OpenRouter, Anthropic, GitHub Copilot and Codex requests.
tailcallhq/forgecode
Writes a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes.
tailcallhq/forgecode
Pulls a GitHub release and every linked pull request, then writes polished, factual release notes from the combined set of changes.
Categories
Creates and structures custom command files for the code-forge CLI, with YAML frontmatter plus special tags for automated lint and test steps. Every command is a single Markdown file placed under the project's forge commands directory, named after the command, and it is the only location forge discovers custom commands from. Each file needs YAML frontmatter with a name and description, plus a body listing the steps to execute in order, written as clear, specific, actionable instructions starting with an action verb.
Code-Forge Command Creator fits situations like: adding a new custom command to a code-forge project; deciding how to name and structure a command file; adding an automated lint or test step to an existing command.
Run `npx skills add tailcallhq/forgecode --skill create-command -a claude-code`. Or copy the skill folder (.forge/skills/create-command in tailcallhq/forgecode) into .claude/skills/create-command in your project. Claude Code loads it when a task matches its description.
Run `npx skills add tailcallhq/forgecode --skill create-command -a codex`. Or copy the skill folder (.forge/skills/create-command in tailcallhq/forgecode) into .agents/skills/create-command in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tailcallhq/forgecode --skill create-command -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-command, .gemini/skills/create-command, .github/skills/create-command and .opencode/skills/create-command in your project.
SKILL.md names no scripts, command-line tools or credentials: Code-Forge Command Creator is instructions for the agent only. Our summary lists: A code-forge project with a commands directory.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Code-Forge Command Creator is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Code-Forge Command Creator: Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars), Dsh Web Documentation (zhu1090093659/dsh-web, 8.4k stars), Harness Engineering Guide (OdradekAI/harness-engineering-guide, 125 stars) and Agent Setup Health Audit (tw93/Waza, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
tailcallhq (a GitHub organization) maintains it in tailcallhq/forgecode, which has 7,642 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.
Source: tailcallhq/forgecode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.