Answer, plan, ratify, or autonomously implement clisbot architecture work from repository evidence. Use when a request may change channel, agent, session, runner, auth, configuration, control, persistence, process, API, UI, integration, ownership, lifecycle, or contract boundaries; when the user asks how clisbot…
Plan, decide, or review names in clisbot with repository evidence for domain terms, APIs, CLI commands, folders, files, functions, variables, classes, types, events, config keys, persisted fields, channel concepts, runner capabilities, UI concepts, and abstractions. Use when the user invokes naming-expert, asks to…
Agent "2026-05-16-hermes-agent-self-evolution" from longbkit/clisbot, covering hermes agent self-evolution research, executive take, what is implemented vs planned, implemented in hermes-agent and implemented in hermes-agent-self-evolution.
Add session-scoped follow-up policy, configurable TTL, and a runtime control API so agents can change conversation behavior dynamically when the user asks.
Evaluate whether broader launch should include a stronger compatibility layer for native CLI slash commands, plus explicit override and customization surfaces when commands conflict.
Agent "2026-05-02-live-session-id-runtime-truth-and-memory-registry" from longbkit/clisbot, covering live session id runtime truth and memory registry, status, priority, summary and why.
Queue-first continuation and review workflow for clisbot queues. Use when work needs deliberate follow-up against early stopping, shallow passes, prompt echoing, history leaking, duplicate files/functions/sections, naming drift, DRY/KISS regressions, missing docs/tests, or bad fallback behavior.
Release clisbot safely to npm and GitHub. Use when Codex is asked to prepare, validate, bump, publish, tag, or document a clisbot beta release, next beta release, or official stable/latest release, including release notes, migration notes, GitHub release notes, npm dist-tags, and post-publish verification.
A skill for opening diffs in difit for user review, or for reviewing a specific diff or PR first and preloading findings into difit as inline comments. Use it after code changes, for commit or branch comparisons, or when a human-readable web diff with anchored comments is the best review surface.