Quick Start

Run the fixed DevHunt CLI in its actual scan, report, and narrate order without stale root scripts.

Prerequisites

The CLI uses Bun and invokes the local GitHub CLI for authenticated GraphQL requests. Install project dependencies and use a least-privilege token whose token-visible repository and pull-request access matches the intended scan. Do not place real tokens in tracked files or command transcripts.

Scan token-visible inputs

Choose the intended login and time window, review the user confirmation, then run scan. --yes or -y skips confirmation and should be reserved for an already-reviewed batch or CI context.

The source applies no public-only visibility filter. Inspect token scope before scanning, and treat all generated output as potentially sensitive.

bun devhunt scan LOGIN --token "$GITHUB_TOKEN" --window year

Build the local report

After scan output exists, run report. The optional --tz value affects local-time activity calculations.

bun devhunt report LOGIN --tz Asia/Shanghai

Prepare a narrative

Run narrate only after reviewing the generated profile and the AI Narrative data boundary.

bun devhunt narrate LOGIN --lang en --style professional

The fixed tree does not contain root dev.sh or build.sh launch scripts. Do not use those stale instructions.