From galeharness-cli
Search and ask questions about your coding agent session history. Use when asking what you worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also use when the user references prior sessions, previous attempts, or past investigations — even without saying 'sessions' explicitly.
npx claudepluginhub wangrenzhu-ola/galeharnesscodingcli --plugin galeharness-cliThis skill uses the workspace's default tool permissions.
Search your session history.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Search your session history.
/gh:sessions [question or topic]
/gh:sessions
Repo and Branch Context:
Determine the current repository name and active git branch before dispatching. You can use native tools or simple safe commands (like git rev-parse --abbrev-ref HEAD) to find them. Do not use complex chained shell substitutions.
If you cannot quickly determine these values, omit them from the dispatch and let the agent derive them at runtime.
If no argument is provided, ask what the user wants to know about their session history. Use the platform's blocking question tool (AskUserQuestion in Claude Code, request_user_input in Codex, ask_user in Gemini, ask_user in Pi (requires the pi-ask-user extension)). If no question tool is available, ask in plain text and wait for a reply.
Dispatch galeharness-cli:session-historian with the user's question as the task prompt. Omit the mode parameter so the user's configured permission settings apply. Include in the dispatch prompt: