zigpeek
Fast CLI for Zig stdlib docs. Uses your local zig when one is on PATH.
Install
uv tool install zigpeek # local zig, or fetch 0.16.0 docs
uv tool install 'zigpeek[offline]' # also bundles 0.16.0 for no-zig hosts
For version pins, --lib-dir, and cache paths, see OTHER-ZIG-VERSIONS.md.
Usage
zigpeek search ArrayList --limit 10 # fuzzy stdlib search
zigpeek get std.ArrayList # full docs for an FQN
zigpeek get std.ArrayList --source-file # source file containing it
zigpeek builtins list # all @-builtins
zigpeek builtins get atomic # specific builtin
zigpeek batch <<EOF # amortize startup
search ArrayList
get std.ArrayList
EOF
When zig is on PATH (or $ZIG / $ZIGPEEK_ZIG), search / get read
that compiler's lib/. Otherwise zigpeek falls back to Zig 0.16.0 from
the [offline] bundle, the XDG cache, or ziglang.org.
Claude Code skill
cp -r skills/zigpeek ~/.claude/skills/
See skills/zigpeek/SKILL.md for the
agent-facing usage.
License
MIT — see LICENSE and ARCHITECTURE.md
for internals.
Credits
The vendored autodoc WASM is built from
zig-wasm/zig-mcp; see
vendor/PROVENANCE.md.
Metadata
Release files for zigpeek 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| zigpeek-0.5.0.tar.gz | 125.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zigpeek-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 213.7 kB
Release files / zigpeek-0.5.0.tar.gz
| Download URL | zigpeek-0.5.0.tar.gz |
|---|---|
| Size | 125.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b31fdcc13b14b123189774a412e50f4d41d5269d9636f266bfdaa7e0dae2ff8f
|
|
BLAKE2b-256 checksum How to use checksums |
cf81bcad431201f5a557ddc9c7bcbc49449564490aff84da85a9ecbe65313853
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 5, 2026.
Transparency logRelease files / zigpeek-0.5.0-py3-none-any.whl
| Download URL | zigpeek-0.5.0-py3-none-any.whl |
|---|---|
| Size | 88.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e37e3f273e2368adbea17ad7e3c2c03c30b71c4b8fd35f30292dd149c2e7d83c
|
|
BLAKE2b-256 checksum How to use checksums |
67c78603413cf2b06198380e80e646e8d0bb4216bf12add64f9e6905db044644
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 5, 2026.
Transparency logSecurity for zigpeek 0.5.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for zigpeek-0.5.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 5, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.