repo-audit

To inspect a GitHub repository safely, this skill first fetches metadata and README content using `gh` CLI to evaluate its size, requiring explicit confirmation before cloning manageable repositories to a temporary sandbox.

Yes, you can analyze a repository's README first. The skill performs a two-stage analysis, initially retrieving metadata and README content via `gh` CLI before optionally proceeding to clone the repository.

Yes, you need both `git` and `gh` installed to audit repository metadata. The skill relies on `gh` CLI for fetching initial repository metadata and `git` for cloning repositories to a temporary sandbox.

The best way to evaluate third-party libraries with disk space constraints is using a two-stage audit that warns about large repositories and requires explicit confirmation before cloning to a temporary sandbox.

Yes, this repository inspection tool prevents accidental large downloads by checking repository size during the metadata fetch stage and only cloning to a temporary sandbox after explicit user confirmation.

The skill clones repositories to a temporary sandbox instead of the current directory to safely inspect potentially massive repositories without risking your main workspace or unnecessarily consuming disk space.