ci/tasks/readme: register fleet
All checks were successful
release-tools / build-release (push) Successful in 2m27s
All checks were successful
release-tools / build-release (push) Successful in 2m27s
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011KikHkfCiC3yELbsMN8fT9
This commit is contained in:
@@ -18,6 +18,7 @@ agent understands the result without opening an image viewer.
|
||||
| [`waitfor/`](waitfor/) | `waitfor` | Blocks until a shell condition holds (exit 0 + optional regex match) — replaces hand-rolled poll loops. `--then` hook composes with notifyr. |
|
||||
| [`cronr/`](cronr/) | `cronr` | Recurring/one-shot jobs as systemd user timers that survive session exit and reboot. add/list/run/logs/rm, schedules validated by systemd-analyze. |
|
||||
| [`giteactl/`](giteactl/) | `giteactl` | Gitea Actions runs, job logs (API/web/ssh+zstd fallback), `wait` (block until green) and `wait-quiet` (the "serialize heavy builds" rule), release assets. |
|
||||
| [`fleet/`](fleet/) | `fleet` | One-shot homelab health snapshot: container states, disk fill and failed systemd units across hosts, via read-only commands. Exit 2 = findings. |
|
||||
|
||||
Each tool has its own folder, its own README with the full format/CLI
|
||||
reference, its own tests and its own dev branch (`dev/<tool>`).
|
||||
@@ -27,8 +28,8 @@ reference, its own tests and its own dev branch (`dev/<tool>`).
|
||||
[`doc/tool-parity.md`](doc/tool-parity.md) compares the Google agent's
|
||||
built-in tools with Claude Code's, and specs the CLI tools that close
|
||||
the gaps so any agent gets the same capabilities via its shell tool.
|
||||
Built so far: `notifyr`, `waitfor`, `cronr`, `giteactl`, `svgc`
|
||||
(2026-08-07). Still on the list: `fleet`, `envaudit`, `reghelper`,
|
||||
Built so far: `notifyr`, `waitfor`, `cronr`, `giteactl`, `svgc`,
|
||||
`fleet` (2026-08-07). Still on the list: `envaudit`, `reghelper`,
|
||||
`pagepub`, `nbcell`, `wtreectl`, `fanout`. Build order and rationale
|
||||
live there and in [`doc/plan.md`](doc/plan.md). Agy finds the tools
|
||||
through the `agent-tools` skill in `~/.gemini/config/skills/`.
|
||||
|
||||
Reference in New Issue
Block a user