Fuzit

Context workflows.

What using Fuzit actually looks like. Concrete examples of how Fuzit engineers repository evidence into deterministic context for local tasks, GitHub PRs, and AI coding tools.

Install Fuzit CLI Reference
EXAMPLE 01

Local Task Context

TASK SCENARIOInvestigate why user sessions expire immediately after a page refresh.

Why it is useful:Eliminates the need to paste whole repositories or manually hunt for scattered files. Fuzit builds the exact subset needed for the task.

COMMAND / INPUT
$ fuzit context --root . \
  --task "investigate session expiration on refresh" \
  --profile bug-fix \
  --budget-tokens 8000 \
  --format markdown \
  --output session-context.md \
  --explain
WHAT FUZIT EVALUATES
  • » Local repository index
  • » Typed graph relationships between SessionContext and refresh events
  • » Semantic relevance to the task string
  • » Security filter rules
WHAT IT PRODUCES
ILLUSTRATIVE CONTEXT TRACE
Selected: src/auth/session.ts (High semantic overlap)
Selected: src/components/Provider.tsx (Imports SessionContext)
Selected: src/hooks/useSession.ts (Graph neighbor)
Omitted: src/ui/Avatar.tsx (Outside task relevance)

A deterministic, bounded context file ready for injection into any LLM.

EXAMPLE 02

GitHub PR Review

TASK SCENARIOGenerate comprehensive context to review a pull request, including the conversation and checks.

Why it is useful:An AI agent looking only at a diff lacks the broader repository intent and team discussion. This workflow acquires both in one command.

COMMAND / INPUT
# Optional: Verify GitHub CLI authentication for private PRs
$ fuzit auth status

$ fuzit review https://github.com/OWNER/REPO/pull/123
WHAT FUZIT EVALUATES
  • » Base and head revisions
  • » Changed files and patches
  • » PR title, body, and thread discussion
  • » Repository relationships to the changed code
WHAT IT PRODUCES
A unified bundle combining the exact code diffs with the reviewer discussions, CI check status, and necessary repository background for an AI to perform a high-level architectural review.

The context isn’t all in the code. Review the work, not just the diff.

EXAMPLE 03

Issue-Driven Context

TASK SCENARIOExtract the implementation context needed to solve a specific GitHub issue.

Why it is useful:Transitions seamlessly from 'bug report' to 'implementation context' without manual discovery.

COMMAND / INPUT
$ fuzit issue 456 --repo OWNER/REPO
WHAT FUZIT EVALUATES
  • » GitHub issue metadata and discussion
  • » Repository source (when available/authorized)
  • » Task intent derived from the issue
WHAT IT PRODUCES

A bounded context model specifically tuned to solve the problem described in the issue, gathering the files the issue references and their graph dependencies.

EXACT CLI WORKFLOW SUITE

Verified CLI Workflows & Output

Real command executions, flags, JSON outputs, pack generators, and task explainability commands evaluated against live codebases.

1. System Readiness Check
fuzit doctor

Verifies local Node.js runtime, platform APIs, Git binary, filesystem permissions, and local index readiness.

$ fuzit doctor
PASS node: Node.js is available.
WARN pnpm: pnpm metadata is unavailable in this process.
PASS platform: Platform metadata is available.
PASS git: Git is available.
PASS filesystem: Working directory is readable and writable.
PASS parser: Built-in parser compatibility is available.
PASS index: Local index compatibility is available.
PASS repository: Repository detected.
PASS configuration: Configuration is valid.
2. Repository Scan Summary
fuzit --json scan

Extracts structured repository statistics, discovered file paths, and metadata in JSON format.

$ fuzit --json scan --root . --summary
{"schemaVersion":1,"root":".","counts":{"files":181,"directories":55,"symlinks":0},"status":"complete"}
3. Repository Packing
fuzit pack

Consolidates filtered code into structured Markdown or JSON payloads with format flags.

$ fuzit pack --root . --format markdown --output .\fuzit-pack.md
✓ Pack created: .\fuzit-pack.md
$ fuzit pack --root . --format json --output .\fuzit-pack.json
✓ Pack created: .\fuzit-pack.json
4. Bounded Context & Explainability
fuzit context --explain

Generates task-specific context under strict token budgets with transparent inclusion receipts.

$ fuzit context --root . --task "Trace authentication flow" --profile architecture-review --budget-tokens 8000 --explain
Selected 4 files (7,999 / 8,000 tokens used). Explanation trace generated.
View Full 23-Command CLI Reference →