experts - Entire

Rank agents, Skills, and tools by their contributions to a file, directory, or topic.

entire experts [SCOPE_OR_QUERY] [flags]

entire experts is experimental and appears under labs while the workflow is still being refined.

Requires a published repository. Entire answers this from its own servers rather than from your local clone, so the repository must be published somewhere Entire can reach and its checkpoints pushed.Publish by creating an Entire repository or by mirroring a GitHub repository, then git push. entire enable does not create or push to a remote for you.Your work becomes available shortly after it reaches Entire, so give a recent push a couple of minutes before treating a missing result as a problem.

Inputs

The argument is either a single scope, meaning a file or directory path, or a natural-language query. One of the two is required unless you pass --staged, which uses your staged file paths as the scopes instead.

Flags

Flag	Description
`--branch NAME`	Branch to inspect.
`--json`	Print JSON.
`--limit N`	Maximum profiles to return, from 1 to 20. Values above 20 are clamped. Defaults to `8`.
`--repo OWNER/REPO`	Repository to inspect.
`--staged`	Use staged file paths as the scopes.
`--tui`	Browse provenance in an interactive viewer. Requires a terminal.

Examples

# Provenance for a directory
entire experts src/payments --json

# Provenance for a natural-language query
entire experts "who owns token refresh"

# Provenance for what you are about to commit
entire experts --staged

The repository must be mirrored.

Continue With

blame

See per-line attribution for a single file.

why

Explain the context behind a file or line.

​Inputs

​Flags

​Examples

​Continue With

blame

why

Inputs

Flags

Examples

Continue With