Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

repo-map

Étoiles2

Forks0

Mis à jour17 mai 2026 à 11:29

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

agentculture

agentculture/code-lens-cli

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

4 fichiers

SKILL.md

readonly

name

repo-map

description

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/connections.sh <path> --depth N` returns typed import / cite / vendor edges N hops out, plus each neighbor node (add `--profile` to inline each node's profile). `scripts/graph.sh [<root>…]` returns every repo + every edge in the workspace plus a mermaid diagram. Markdown by default; `--json` for machine-readable. Prefer this over multiple Read/Bash calls whenever you need ≥2 of those fields — one call beats N reads on both tokens and reliability, and the output is deterministic so you don't have to defend grep-based guesses.

repo-map

Three verbs, scaling from cheap (one repo, mechanical facts) to opt-in expensive (entire connected component with deep mind-model materials):

Mode	Invocation
One repo, mechanical facts	`scripts/profile.sh <path>`
One repo, mind-model materials	`scripts/profile.sh <path> --depth deep`
Walk N hops from a repo	`scripts/connections.sh <path> --depth N`
Whole workspace at once	`scripts/graph.sh [<root>...]`

When to use

When the user asks about a repo or a set of related repos: profile, deps, who-cites-whom, who-vendors-whom. The scripts collect the deterministic facts so you (the agent) can spend your tokens on synthesis, not grep.

Token math: one profile.sh call replaces ~6–10 separate Read calls (README.md, pyproject.toml, CHANGELOG.md, CLAUDE.md, docs/skill-sources.md, CITATION.md, culture.yaml, plus directory listings for the package tree and vendored skills). If your task needs ≥2 of those, call profile.sh once instead of reading them piecemeal.

When NOT to use

You already know the exact file you need to read (e.g. one specific function's source) — Read it directly.
You need to modify the repo — repo-map is read-only.
The repo isn't a Python project (no pyproject.toml) — profile degrades but the mechanical-facts payload shrinks to mostly empty.

Compose recipe

For the question "explain how these repos fit together":

scripts/graph.sh [<root>] once — gets every repo + every edge.
If a particular repo needs depth, scripts/profile.sh <path> --depth deep.
Synthesize the narrative from those outputs. Do not re-grep what profile already reports.

For the question "tell me about this repo and what it connects to":

scripts/profile.sh <path> (or --depth deep for narrative-rich).
scripts/connections.sh <path> --depth 1 --profile for immediate neighbors; raise --depth to widen.

Output

Markdown by default — read it directly. Errors include reason: and hint: lines. During walks, per-node errors are inlined and the walk continues (pass --strict to flip).

Configuration

Optional .claude/skills/repo-map/config.json for per-workspace defaults:

{
  "roots": ["$HOME/git"],
  "additional_markers": ["culture.yaml"],
  "skip_dirs": [".git", ".venv", "node_modules", "__pycache__"],
  "default_connections_depth": 1
}

Flags always override config.

Engine

The actual logic lives in code_lens/repo/ and is invoked via uv run python -m code_lens.repo <verb>. The shell scripts are one-line wrappers; the agent-facing contract is the verbs and their flags, not the wrappers.

Interpreter note: the scripts use uv run --directory <project-root> so they work regardless of the caller's working directory. uv resolves the correct virtualenv and lock file from the project root automatically.

Plus depuis ce dépôt

même dépôt

recall

agentculture/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

2026-06-232

remember

agentculture/code-lens-cli

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

2026-06-232

cicd

agentculture/code-lens-cli

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.

2026-05-172

code-lookup

agentculture/code-lens-cli

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`

2026-05-172

communicate

agentculture/code-lens-cli

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.

2026-05-172

run-tests

agentculture/code-lens-cli

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

2026-05-172

name

repo-map

description

repo-map

Three verbs, scaling from cheap (one repo, mechanical facts) to opt-in expensive (entire connected component with deep mind-model materials):

Mode	Invocation
One repo, mechanical facts	`scripts/profile.sh <path>`
One repo, mind-model materials	`scripts/profile.sh <path> --depth deep`
Walk N hops from a repo	`scripts/connections.sh <path> --depth N`
Whole workspace at once	`scripts/graph.sh [<root>...]`

When to use

When NOT to use

You already know the exact file you need to read (e.g. one specific function's source) — Read it directly.
You need to modify the repo — repo-map is read-only.
The repo isn't a Python project (no pyproject.toml) — profile degrades but the mechanical-facts payload shrinks to mostly empty.

Compose recipe

For the question "explain how these repos fit together":

scripts/graph.sh [<root>] once — gets every repo + every edge.
If a particular repo needs depth, scripts/profile.sh <path> --depth deep.
Synthesize the narrative from those outputs. Do not re-grep what profile already reports.

For the question "tell me about this repo and what it connects to":

scripts/profile.sh <path> (or --depth deep for narrative-rich).
scripts/connections.sh <path> --depth 1 --profile for immediate neighbors; raise --depth to widen.

Output

Markdown by default — read it directly. Errors include reason: and hint: lines. During walks, per-node errors are inlined and the walk continues (pass --strict to flip).

Configuration

Optional .claude/skills/repo-map/config.json for per-workspace defaults:

{
  "roots": ["$HOME/git"],
  "additional_markers": ["culture.yaml"],
  "skip_dirs": [".git", ".venv", "node_modules", "__pycache__"],
  "default_connections_depth": 1
}

Flags always override config.

Engine

Interpreter note: the scripts use uv run --directory <project-root> so they work regardless of the caller's working directory. uv resolves the correct virtualenv and lock file from the project root automatically.