Claim a Forge issue and then PROVE you hold the live lease before you touch it, using forge issue owns (exit 0 iff you hold the single unexpired lease). Use this whenever winning the claim matters: right after forge claim, before you dev/edit/close/release a claimed issue, when two agents or a subagent fan-out contend…
Forge DEV stage — implement an already-planned /plan task list into committed, test-backed code. Reads tasks.md + plan.md, then drives each task through a subagent TDD loop (implementer → spec-compliance reviewer → code-quality reviewer) with RED-GREEN-REFACTOR, HARD-GATE evidence checks, and a spec-gap decision…
Toggle Forge's workflow gates and rails — strong-but-toggleable enforcement. forge gate enable|disable flips workflow.gates. .enabled in .forge/config.yaml; the installed git hooks read resolved config at run time, so disabling a rail makes them genuinely inert. forge gate approve|reject records durable human-gate…
Hermes⇄Forge boundary: Hermes CONSUMES Forge state, never a second source of truth. Use whenever a Hermes session runs on a Forge repo: at session start, before acting on an issue, or when you need CURRENT state. Read state ONLY via forge orient / forge recap (bounded JSON envelope), citing each source's…
Everyday single-issue CRUD over the forge issue verbs: create/update/show/list/search/close/reopen/comment, set priority/labels/assignee, claim or release one issue, add/remove dependency edges, plus backlog stats. Use for ANY routine one-off issue op: "create an issue/bug/task for X", "update/edit issue ", "close or…
Forge kernel — umbrella index/router for a Forge project. Reach for this FIRST when orienting rather than executing: at session start, when you need the map of how the system fits together, or when unsure WHICH skill or forge verb a task belongs to. It indexes smith (end-to-end orchestrator), the stage ladder (plan →…
Capture and retrieve durable project memory the right way -- and, when the graph backend is enabled, use temporal knowledge-graph memory. Reach for this whenever you are about to write down a lasting fact, decision, convention, or gotcha ("remember that...", "note for later", "save this"), or when you need to recall…
Heavyweight EXTERNAL research reports — market, industry, competitive, strategic — via Parallel AI's paid pro/ultra processors that crawl and synthesize dozens of sources into one long cited report. Use when the user wants a market analysis, competitive landscape, industry deep-dive, multi-vendor/technology…
Forge PLAN stage — first stop when starting a NEW or unscoped feature. Sets up an isolated worktree up front, then runs one-question-at-a-time brainstorming for design intent, commits a design doc, does technical/OWASP/DRY + codebase research, and produces a TDD task list for /dev. Trigger on "let's plan X", "scope a…
Forge kernel data portability — getting issue data in and out of the local kernel. forge export [--dir] [--dry-run] writes the kernel backlog to deterministic git-tracked JSONL (D16 portability projection); forge export --import reads that committed snapshot back into the kernel (hydrate). forge migrate --from beads…
Forge RESEARCH — a first-class, freely-invocable investigation skill any agent can call standalone OR mid-workflow (mid-/dev, mid-/validate, mid-/plan), not a plan-only stage. Use it to verify/fact-check a claim against primary sources; web-search best practices, gotchas, and docs; find better options/patterns and…
Drive an already-open PR's feedback and failing checks to all-green, resolve every thread, run the pre-merge doc gate, then stop for manual merge. Use only when the user asks to address PR feedback or checks; never merges or substitutes for Shepherd monitoring.
Safely undo committed or shipped changes with non-destructive git revert or restore. Use only when the user explicitly asks to roll back, revert, undo, back out, or restore; never reset hard, force-push, or substitute for PR review, monitoring, or issue status work.
Forge install & setup lifecycle. forge setup interactively configures Forge for your coding agents; forge init [--profile minimal|standard|full] writes the adoption config in a fresh repo; forge doctor reports whether the kernel DB is on a cloud/network path; forge upgrade [--dry-run] previews + self-heals upgrade…
Own open PRs to merge-readiness — autonomously. Forge provides a singleton shepherd daemon — start it with forge shepherd daemon — that then watches every open PR, converges CI check state into kernel verdicts, re-runs flaky required checks, reaps orphan watchers, and self-retires when no PRs remain; one-shot passes…
Push a validated feature branch and open its PR from the project's template, then stop for manual merge. Use only when the user asks to ship or open the PR after validation; never merges, auto-merges, reviews an existing PR, or replaces end-to-end Smith.
The flagship Forge orchestrator: given a goal or a ready issue, it composes the stage skills (triage-ready · claim-safety · plan · dev · validate · ship · review · verify) into the right path for the work, running autonomously between human gates and pausing at them. Use this whenever the user wants to work the next…
SonarCloud deep-dive via its REST API: pull open issues (bugs, vulnerabilities, code smells), coverage/duplication metrics, quality-gate pass/fail with failed thresholds, security hotspots, and measure/analysis history for a whole project, branch, or PR, then return a ranked summary. Use whenever the user names…
Query SonarCloud code-quality data via the /sonarcloud slash command — the fast in-context lookup for a project, branch, or PR. Handles issues, metrics, gate (pass/fail + failed conditions), health, pr , hotspots, history, plus --branch, --severity, --type, --new-code filters. Use the moment the user types /sonarcloud…
Report where the project stands and what work is in flight -- the Forge status snapshot. Reach for this at session start or whenever the user says "/status", "where am I", "what's in progress", "catch me up", "resume work", or "what changed recently". It surfaces the workflow stage, your active/claimed issues, all…
Surfaces, ranks, and EXPLAINS the single best next issue in a Forge project — strictly read-only. Recomputes the live ready queue and explains what is blocked via forge issue ready/blocked/stats/show, always against the live kernel, never forge board. Recommends ONE issue with a one-line reason, then hands off; never…
Forge dispatch skill: the session bootstrap that makes Forge's skills auto-trigger as a reasoning-driven SYSTEM. Reach for this FIRST, before ANY response (including clarifying questions, codebase exploration, or file reads), whenever there is even a 1% chance a Forge skill applies. Carries the 1%-rule, the…
Forge VALIDATE stage — the pre-pull-request quality gate. Rebases the branch onto the current base branch, then runs type-checking, linting, code review, an OWASP Top 10 security review plus dependency scan, and the full test suite, demanding fresh passing output in THIS session before anything ships. Reach for this…
Runs the Forge verify stage — the post-merge health check performed AFTER a PR is merged: switch to master and pull, confirm the merge landed, check CI is green on master, confirm deployments are up, remove the merged worktree, safe-delete the branch, and close the kernel issues the PR resolved. Use when asked to…