feat: add cli-anything-everything — agent-native CLI for Everything file search

[jueduilunhui]

Type

• New Software CLI (standalone repo) — registry-only PR

Description

Adds cli-anything-everything to the CLI-Hub registry — an agent-native CLI for Everything file search on Windows.

Features

• ✅ JSON output — structured, machine-readable results for AI agents
• ✅ GBK→UTF-8 — auto-converts Chinese Windows encoding
• ✅ REPL mode — interactive search with prompt-toolkit
• ✅ WSL-ready — detects and uses WSL paths for cross-environment execution
• ✅ Full Everything syntax — regex, case, whole-word, path matching, date filters

Checklist

• CLI is installable via pip install git+https://github.com/jueduilunhui/cli-anything-everything.git
• SKILL.md exists at https://raw.githubusercontent.com/jueduilunhui/cli-anything-everything/main/SKILL.md
• External repo has its own test suite (21 tests passing)
• registry.json entry includes source_url pointing to external repo
• install_cmd tested locally
• --json flag supported on all commands

Repo

https://github.com/jueduilunhui/cli-anything-everything

Test output

21 passed in 0.04s

Category

search

[yuh-yang]

Thanks for adding the Everything CLI. I verified the external repository and raw SKILL.md URL are reachable.

One registry-structure issue blocks merge: this is a standalone external CLI, but the PR adds it to registry.json. Please move the entry to public_registry.json unless maintainers explicitly want this external package in the in-repo harness registry.

After that, please include a short clean-environment smoke note for:

• pip install git+https://github.com/jueduilunhui/cli-anything-everything.git
• cli-anything-everything --help
• one safe JSON command on a machine without Everything running, showing it fails cleanly.

[omerarslan0]

Echoing @yuh-yang's blocking comment — this entry belongs in public_registry.json, not registry.json. Convention in registry.json is in-repo agent-harness packages installed via pip install git+https://github.com/HKUDS/CLI-Anything.git#subdirectory=<name>/agent-harness; external standalone repos go in public_registry.json.

Additional items before re-review:

1. Move the entry to public_registry.json. Drop the registry.json change entirely.
2. The diff removes the trailing newline on registry.json (\ No newline at end of file). Restore it — even after moving the entry out, do not leave the file without a final newline.
3. entry_point is "cli-anything-everything". Confirm this matches the actual console script declared in the external repo's pyproject.toml/setup.cfg. The name is unusually long for an entry point.
4. requires says "Everything 1.4+ installed and running with es.exe" but does not state OS constraint. Add Windows (native or WSL) explicitly so agents can gate on platform.
5. Provide the clean-environment smoke output yuh-yang asked for: pip install from a fresh venv, --help, and one --json command on a host without Everything/es.exe running showing a structured non-zero exit.
6. External repo was created on the same day as this PR with 0 commits since. Please link to at least one tagged release (or pin install_cmd to a specific commit SHA) so the registry entry is reproducible.

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[yuh-yang]

Thanks for moving this external CLI entry from registry.json to public_registry.json; that fixes the main registry-structure issue.

A few items still block merge:

• Please rebase and resolve the current public_registry.json conflict.
• Please make the install reproducible. The external repo currently has no tag/release, and the registry install command is still an unpinned git+https://... URL.
• Please clarify the platform requirement in requires, since Everything/es.exe is Windows-specific or WSL-dependent.
• When es.exe is unavailable, cli-anything-everything --json search ... prints a structured JSON error but exits with code 0; machine consumers need a non-zero exit for this failure.
• Please clean up the external package author metadata (zero <zero@example.com>) so it matches the actual project/contributor identity.

I verified the external package installs and its tests pass, but I would not merge until the registry conflict and smoke-failure semantics are fixed.

[yuh-yang]

No new changes appear after the last maintainer review, so the same blockers still apply:

• Please rebase and resolve the current public_registry.json conflict.
• Please make the install reproducible. The external repo still needs a tag/release or a pinned commit in the install command.
• Please clarify Windows/WSL requirements in requires, since Everything/es.exe is platform-specific.
• When es.exe is unavailable, cli-anything-everything --json search ... should exit non-zero instead of returning a JSON error with exit code 0.
• Please clean up the external package author metadata so it no longer uses placeholder identity.

Once those are fixed, please include a clean install/help/JSON failure-mode smoke note.