Menu
Move one bounded cmd/gormes command domain out of root files toward root main.go only. Use when thinning cmd/gormes, burning down loose root files, preserving CLI behavior, or catching refactor regressions during cmd moves.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Implement one selected repo-scoped Gormes row with tests. Use when next-work says decision=build. Do not use for decision=plan, broad parity audits, or untracked feature ideas.
Shape source-backed Gormes progress rows. Use for decision=plan builder handoffs, row splitting, feature maps, or parity planning. Do not use when decision=build or for runtime code.
Route Gormes work to the smallest repo-local skill chain. Use before substantial planning/building/refactor work, when unsure which Gormes skill applies, or when creating/improving repo-local skills.
Build one selected Gormes behavior with red-green-refactor. Use when the row or reproduced bug defines a test target. Do not use after decision=plan or for broad planning.
Use when an agent is unfamiliar with a Gormes code area, a change crosses package boundaries, or a refactor needs a source-backed module map before edits.
Plan or implement browser automation parity. Use for Browser Use, go-browser-harness, CDP, /browser connect, browser providers, tool descriptors, and browser interaction skills.
| name | cmd-internal-refactor |
| description | Move one bounded cmd/gormes command domain out of root files toward root main.go only. Use when thinning cmd/gormes, burning down loose root files, preserving CLI behavior, or catching refactor regressions during cmd moves. |
Move exactly one cmd/gormes command domain without behavior changes. A domain is not one file: when the user says "too slow", "refactor all", or supplies a file list, use accelerated same-domain mode to select the largest cohesive domain cluster from that list, move its directly owned behavior/tests/facades in one pass, validate once, then stop before a second domain. Start every move with a bug-finding oracle: capture the selected command's current observable behavior, add/keep characterization tests for risky seams, and rerun the same evidence after extraction.
Thin cmd/gormes toward this final topology:
cmd/gormes/main.go: executable shim and root factory delegation only. Other tracked root entries, including docs such as codemap.md, must be rehomed or explicitly classified before final topology claims.internal/platform/cli/gormescli: Cobra wiring, flags, args, help, command registration, exit-code seams, CLI/golden tests, root test helpers.internal/app/<domain>: command-local behavior, options/results, formatting/path/env helpers, behavior tests.internal/<runtime-domain> packages: reusable gateway, provider, session, persistence, memory, TUI, channel, and tool runtime behavior.This is refactor-only, not blind relocation. Use the move to expose regressions and preexisting defects, but preserve current Gormes behavior unless the refactor itself introduced the bug. If a slice needs intentional behavior changes, split them out and route through planner/builder/TDD.
repo=$(git rev-parse --show-toplevel)) and run discovery from there; the current cwd may already be inside cmd/gormes.development; do not create branches or worktrees.git -C "$repo" status --short --branch --untracked-files=all; preserve unrelated dirty work.folder_refactor_scan on the absolute $repo/cmd/gormes path before planning; otherwise list root files and subdirectories explicitly.hermes-knowledge-graph.json exists and is readable, then query it only for the selected domain. If the graph is missing or unreadable, stop.Candidate table columns:
domain | cmd files/tests | Hermes graph refs or Gormes-owned evidence | dirty/topology risk | extraction slice | decision
Prefer, in order:
internal/ and the slice burns down root CLI or behavior tests;Skip domains needing live credentials, persistence migrations, gateway runtime changes, public contract changes, or multi-domain edits to validate.
Use this mode to avoid slow one-file passes while still preserving the one-domain stop rule.
setup.go or setup_profiles_tui.go contains multiple subflows, first carve out the selected subflow through narrow root adapters; do not attempt a whole-file migration unless every subflow in the file belongs to the selected domain.See Acceleration guide for examples and anti-patterns.
Use the extraction to catch defects without smuggling in behavior changes.
GORMES_HOME and no live credentials.See Bug-finding during refactor for bug traps, triage, and verification examples.
Read domain-folder-topology.md after selecting the domain. Enforce:
cmd/gormes/main.go -> internal/platform/cli/gormescli -> internal/app/<domain> -> deeper internal runtime packages
cmd/gormes, gormescli, or other CLI platform packages.gormescli may import internal/app/<domain> and lower-level runtime packages.gormescli facades to reduce root direct-internal imports and avoid app↔CLI cycles.cmd/gormes/<domain> subpackages are migration candidates, not the endpoint.codemap.md; rehome/update documentation references before claiming main.go only.cmd/gormes entry, then selected-domain files/tests.hermes-knowledge-graph.json for matching Hermes command/domain files, symbols, and summaries; if none exist, classify the domain as Gormes-owned/no-Hermes-analogue only with explicit local evidence.internal/platform/cli/gormescli.internal/app/<domain>.internal/ packages.main.go factories/seams only; delete moved loose root files instead of leaving wrappers. Thin root adapters are allowed only when a larger root file still contains other domains.go test ./internal/support/repochecks -run 'Cmd|Internal|Topology|Import' -count=1.Use focused gates from the topology reference first, then go run ./cmd/progress validate and git diff --check. A passing gate must include the selected domain's before/after bug oracle when behavior moved; compile-only is insufficient unless the slice is tests-only or helper-only. Full go test ./... / go vet ./... is closeout-only when unrelated dirty/concurrent work cannot invalidate the result. Never claim full-repo green when broad unrelated dirty work is active.
Stop when preserving the CLI contract requires behavior changes, tests need live credentials/user state, more than one domain must move, public config/persistence/provider/gateway/TUI contracts would change, a subpackage would import root cmd/gormes, an app→CLI dependency cycle appears, the Hermes graph file is missing/unreadable, a graph-backed domain lacks graph evidence, a no-Hermes-analogue claim lacks local evidence, a preexisting bug fix would be needed to complete the refactor, tests/golden expectations must be weakened to pass, or unrelated dirty files make validation/commit scope unsafe.
Report selected domain, whether accelerated same-domain mode was used, moved/created/reused files, Hermes graph refs or Gormes-owned no-analogue evidence, preserved CLI boundary, root-file burn-down before/after, remaining root/deeper file classifications, dependency-cycle/import-budget notes, tests added or moved, bug findings classified as none/preexisting/introduced/parity-drift with evidence, validation results, skipped validation with reasons, deferred files from any supplied list, and whether root cmd/gormes is complete (main.go only) or still incomplete.
Before claiming complete topology, run folder_refactor_audit when available and classify every remaining root basename as main.go facade, intentionally out of scope, or next move/extraction candidate.