code-lens-cli

Search the shared eidetic memory store and get back ranked, provenanced records. Drives `eidetic recall` with four search modes — exact (verbatim substring), approximate (vector/semantic), keyword (BM25 lexical), and hybrid (a weighted blend of vector+keyword, the default) — each hit carrying its text, full metadata, a relevance `score`, and a freshness `signal`. Recall passively reinforces matched records (bumps last_recall + recall_count). Shadowed and archived records are excluded by default; use --include-shadowed / --include-archived to retrieve them. The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree); the wrapper defaults queries to this agent's PERSONAL, PRIVATE scope (`--scope code-lens-cli --visibility private`, suffix read from culture.yaml) — matching where /remember writes — so a no-flag recall returns this agent's own private records plus the shared public pool, and Claude and the colleague backend recall each other's memories because both resolve the same suffix via

Ingest records into the shared eidetic memory store so they can be recalled later. Drives `eidetic remember`: accepts one record as a JSON object, or a batch as NDJSON on stdin for bulk ingest. Upsert is idempotent by id (and dedups by content hash) — re-remembering updates in place, never duplicates. Stamps a `created` date on every record at ingest time. Accepts `supersedes` (id of the record this one replaces, for within-scope shadowing via `sweep`) and `links` (list of related-memory ids). The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree), and the wrapper defaults records to this agent's PERSONAL, PRIVATE scope (`--scope code-lens-cli --visibility private`, suffix read from culture.yaml) so they don't leak to a default/other-scope recall — Claude and the colleague backend still share them because both resolve the same suffix via this skill. Pass `--visibility public` to contribute to the shared public pool instead. Use when the user says "remember this", "store this", "save t

Steward's CI/CD lane, layered on `agex pr`. Delegates lint / open / read / reply / delta to agex; adds two steward extensions — `status` (SonarCloud quality gate + hotspots + unresolved-thread tally) and `await` (read --wait + status with non-zero exit on Sonar ERROR or unresolved threads). Use when: creating PRs in steward, handling review feedback, polling CI status, or the user says "create PR", "review comments", "address feedback", "resolve threads". Renamed from `pr-review` in steward 0.7.0; rebased on agex in 0.12.0.

Pick the verb by the question you're asking, not the tool you'd otherwise reach for. Three questions, three one-call answers: **"What changed in the last N commits — which functions or classes did each commit add, remove, or modify?"** → use `recent`, **not** `git log` + `git show` + manual diff reading. `scripts/recent.sh [<path>] [-n N]` returns `{"commits": [{"sha","date","subject","changes":[{"file","added","removed","modified"}, …]}, …]}` — the symbol diff is computed via AST, so you skip the manual "what functions changed" step. The `modified` heuristic compares function line-spans; pure line shifts can cause false positives (a deferred improvement). **"Where is `<pattern>` referenced — and what function or class owns each match?"** → use `grep`, **not** `rg`/`grep` + Read each file to find the enclosing scope. `scripts/grep.sh <pattern> [<path>]` returns `{"pattern","matches":[{"file","line","scope","text"}, …]}` — `scope` is the enclosing Python function or class, resolved via AST. Requires `ripgrep`

Cross-repo + mesh communication from steward: file tracked GitHub issues on sibling repos, fetch issues from sibling repos to inline current state into briefs, and send live messages to Culture mesh channels. Use when the next step lives outside steward (a brief for a sibling-repo agent, a status ping for a Culture channel, or pulling an issue body + comments into context). Issue posts auto-sign with `- steward (Claude)`; mesh messages are unsigned (the IRC nick is the speaker). Not for in-steward issues — use `gh issue create` or the `cicd` skill for those. Renamed from `coordinate` in steward 0.8.0; absorbed `gh-issues` in 0.9.1. Issue I/O is backed by `agtag` (>=0.1) starting in 0.11.0.

Mechanical facts about a Python repo or a workspace of related repos — in one tool call, instead of N grep/read calls. `scripts/profile.sh <path>` returns: package name, version, repo path, manifest type + language, entry points, runtime + dev deps, flat package layout, depth-2 package tree, build_test (test cmd + coverage gate + python_requires), ci_workflows, publish_target (PyPI/GHCR + trigger), git_remote (host/owner/repo parsed from origin), module_summaries (per-module first-docstring-line summaries), vendored skills with upstream provenance, last 3 changelog entries, CITATION.md table, CLAUDE.md "Project status" body, extras (culture nick, …); with default online enrichment, also returns `github_state` (latest release, open issue count, default branch, CI status on default) and `pypi_state` (published version + release date). Pass `--basic` to skip Tier-2 and return Tier-1 mechanical facts only. Add `--depth deep` for: README intro, design-related CLAUDE.md sections, last 10 commit subjects. `scripts/c

Run pytest with parallel execution and coverage. Use when running tests, verifying changes, or the user says "run tests", "test", or "pytest".

Query SonarCloud API for code quality data. Use when: checking quality gate status, fetching code issues or security hotspots, reviewing metrics (coverage, bugs, code smells), or the user says "sonar", "quality gate", "code quality", "sonarclaude".

Bump the semver version in pyproject.toml (major, minor, or patch) and prepend a Keep-a-Changelog entry to CHANGELOG.md. Use when preparing a release, before creating a PR (the version-check CI job blocks merge if you don't), or when the user says "bump version", "release", or "increment version".