Onefetch CLI
The CLI summarizes a local Git repository and its code statistics to give agents a concise starting point for project exploration.
- 12,088 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The utility reads local files and Git history; saved summaries can expose private project information.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/onefetchDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The utility reads local files and Git history; saved summaries can expose private project information.
This is third-party code. Review the repository files before installing.
What it does
Onefetch prints a summary of a local Git repository. Users receive project information and code statistics to share with an agent before deeper source inspection. It works offline against the available local copy. Output fields and appearance are configurable, with file and directory exclusions. JSON and YAML are available alongside terminal output. The summary helps orient the reader to project languages and history, while architecture still requires code and documentation review.
Who it is for. People joining a Git project who need a concise repository summary before exploring code with an agent.
Good fit when
- An agent needs basic context before reading a local repository.
- A user compares language composition across projects.
- A report needs repository statistics as JSON or YAML.
- Generated directories should be excluded from the summary.
Not a fit when
- The repository is not available locally.
- A statistical summary must establish code quality or security.
- The task requires creating commits or changing Git history.
Example request
Summarize this local repository and explain excluded directories before examining its architecture.Limitations
Onefetch analyzes a local Git copy, so information freshness follows that copy’s state. Programming and markup languages are shown by default; prose and data formats need explicit inclusion through `--type`. One author using different names or email addresses can appear multiple times until mapped with `.mailmap`. File and directory exclusions change statistical coverage, so keep settings consistent when comparing repositories.
How to disable. Stop invoking Onefetch from agent commands or shell startup. Remove saved report files separately if needed.
FAQ
Is internet access required?
No. Onefetch works with a local Git repository.
How do I select a repository?
Pass its path, as in `onefetch /path/of/your/repo`.
Why are Markdown or JSON missing?
Prose and data types are hidden by default; include them with `--type`.
Why does one author appear twice?
Their name or email can differ in Git history. Use `.mailmap` to unify identities.
Can I get machine-readable output?
Yes. JSON and YAML output are supported.
Discussion
No questions or reviews yet.
Related
CLI toolsA CLI that opens a local git diff in the browser like GitHub's Files changed tab; comments copy out as prompts for an agent
Oil Git shows branches, changes and diffs in a separate window, and an agent opens a project with the oil-git command.
An MCP server builds a graph of code entities, relations and flows so the agent finds the right files without reading everything
A CLI that records coding-agent steps and links file lines to the tool call, conversation and original request behind them.
A CLI turns Git changes into a guided code walkthrough with questions and explanations written by your existing agent
The CLI counts code, comments and blank lines by language so an agent can describe the selected repository’s makeup.
README in short
Styling and individual information rows are configurable. Binaries cover Linux, macOS and Windows.