yukta / cli
CLAUDE.md1 starsChanged 20 days agoApache-2.0View on GitHub
Windows: the Makefile and the Gradle go* tasks need a POSIX shell with make, awk and grep (WSL or Git Bash). The released .exe is cross-built and needs none of them. Exit codes (a contract for scripts): 0 ok, 1 other failure, 2 usage, 3 not found (404), 4 server (5xx), 5 timeout. -o accepts table or json.
In this repository21 other files it gives its agents.
- architecture/CLAUDE.mdCLAUDE.md
- boot/CLAUDE.mdCLAUDE.md
- build-logic/CLAUDE.mdCLAUDE.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- core/CLAUDE.mdCLAUDE.md
- mcp/CLAUDE.mdCLAUDE.md
- messaging/CLAUDE.mdCLAUDE.md
- plugin-api/CLAUDE.mdCLAUDE.md
- plugins/CLAUDE.mdCLAUDE.md
- plus/CLAUDE.mdCLAUDE.md
- ui/CLAUDE.mdCLAUDE.md
- web/CLAUDE.mdCLAUDE.md
- ide-index-mcpSkill
- pickupSkill
- playwrightSkill
- testsSkill
- ticketSkill
- yuktaSkill
- yukta-supervisorSkill
- yukta-workflowsSkill
The file
Files
Yukta Go CLI CLAUDE.md
Overview
A lightweight, cross-platform command-line interface (CLI) for Yukta, built in Go.
Build & Development Commands
Gradle Commands
# Build for current platform
yk gradle :cli:goBuild
# Build for all platforms
yk gradle :cli:goBuildAll
# Run Go tests
yk gradle :cli:goTest
# Run all Go checks (format, vet, lint, security, vuln scan) — wired into :cli:check
yk gradle :cli:checkMakefile Commands (from cli/ folder)
make build # Build for current OS/arch
make build-all # Build for all platforms
make test # Run Go tests
make lint # Run Go linters
make fmt # Format codeWindows: the Makefile and the Gradle go* tasks need a POSIX shell with make, awk and grep (WSL or Git Bash). The released .exe is cross-built and needs none of them.
Exit codes (a contract for scripts): 0 ok, 1 other failure, 2 usage, 3 not found (404), 4 server (5xx), 5 timeout. -o accepts table or json.
Project Structure
cmd/yukta/main.go: Entry point.internal/commands/: Command definitions (Cobra).internal/client/: HTTP client and types.internal/app/: Application configuration.internal/notify/runs the OS notifier (notify-send,osascript, PowerShell) and the--execcommand through an injectableRunner, never through a shell;commands/notificationsholdsnotifications list|read|dismissandnotify;client.StreamNotificationsreopens the stream with the last event id forever (followSSEFrom).- Go tools through
yk: this checkout's dev server has noGOPATH/HOME, so runyk tool -C cli env GOPATH=$HOME/go GOCACHE=$HOME/.cache/go-build HOME=$HOME go test ./...(andmake cover-check|lint|sec|vuln|fmt-checkthe same way). - Dogfood scripts (yukta-dogfood) are thin wrappers over this CLI: if they need a server call the CLI lacks, add it here (
controlbus watch,workflow node retry|signal|breakpointcame from that).:cli:checkenforces 100% coverage per function.controlbus watch --quietmust keep passingHEALlog lines (the self-healing check's fix reports) next to problems. ../docs/contributing/modules/cli.mdx(module guide); open risks, bugs and review findings: GitHub issues labelledcli(gh issue list -l cli; risks also carryrisk); evolution path and quality lenses:../design/assessments/cli.md.
Tech Stack
- Go 1.26
- Cobra (CLI framework)
Imports
@.claude/rules/git-workflow.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

