longbkit/clisbot

Agentic Coding CLI & chat bot

114Stars on the repository
23Mods indexed here, across every type
2d agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

architect

01

longbkit/clisbot

Skill Claude CodeCodex

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…

114 2d ago A 99 tokens original MIT

naming-expert

02

longbkit/clisbot

Skill Claude CodeCodex

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…

114 2d ago A 125 tokens original MIT

queue-workflow

03

longbkit/clisbot

Skill Claude CodeCodex

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.

114 2d ago A 62 tokens original MIT

release-clisbot

04

longbkit/clisbot

Skill Claude CodeCodex

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.

114 2d ago A 74 tokens original MIT

web-diff-review

05

longbkit/clisbot

Skill Claude CodeCodex

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.

114 2d ago A 66 tokens original MIT