ov-layers/skills/forgecode/SKILL.md
Forge AI coding agent CLI (forgecode.dev) installed globally via npm from the `forgecode` package. Installs the `forge` binary. Use when working with Forge, forgecode.dev, or alternative AI coding agents.
npx skillsauth add overthinkos/overthink-plugins forgecodeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Property | Value |
|----------|-------|
| Dependencies | nodejs |
| Install files | layer.yml, package.json |
| npm package | forgecode |
| Installed binary | forge (at ${HOME}/.npm-global/bin/forge) |
# image.yml
my-dev:
layers:
- forgecode
hermes-full (metalayer) -- bundles forgecode alongside claude-code / codex / geminihermes image -- ships forgecode transitively via hermes-full/ov-layers:nodejs -- required dependency (provides npm)/ov-layers:claude-code, /ov-layers:codex, /ov-layers:gemini -- sibling AI CLIs (same npm-global install pattern)/ov-layers:hermes-full -- metalayer that bundles this CLI/ov-images:hermes -- primary image that ships this CLI/ov:layer -- layer authoring reference/ov:test -- declarative testing framework (this layer verifies ${HOME}/.npm-global/bin/forge + forge --version)Use when the user asks about:
forgecode layerdevelopment
Claude Code multi-agent support in Overthink — sub-agents, dynamic workflows, and agent teams, and how each drives the existing `ov eval` disposable beds to test and verify. MUST be invoked before authoring or invoking an ov sub-agent / dynamic workflow / agent team, wiring agent-lifecycle hooks, or asking "which primitive should drive the R10 beds?".
tools
Mounts a virtiofs share tagged `workspace` at /workspace inside a VM guest via a systemd .mount unit. Use when a kind:vm entity shares a host directory into the guest and you need it auto-mounted (and re-mounted at every boot).
development
MUST be invoked before any work involving: the `kind: android` schema kind, a `target: android` deploy, the `apk:` layer package format (installing Android apps declaratively), AndroidDeployTarget, an in-pod emulator OR a remote/physical adb-endpoint device, or nested `pod → android` deployment. The first-class Android device + app surface that sits above `ov eval adb`/`appium`.
tools
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + image/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.