fux-answer

Generates cited answers from a git-committed document index using fux answer and fux verify.

1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/arpitarya/fux --skill fux-answer-arpitarya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fux-answer
Source: https://github.com/arpitarya/fux/tree/main/.agents/skills/fux-answer
Command: npx skills add https://github.com/arpitarya/fux --skill fux-answer-arpitarya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you need an answer grounded in your team's written knowledge — runbooks, specs, decisions — with exact line citations and proof the source text is still current, this Skill runs fux answer to read the top-ranked documents from their sources and returns verbatim passages with freshness verdicts, then uses fux verify to reproduce or audit that answer later. ## Core Features & Use Cases - Cited answers with line-range locators: fux answer "<q>" --json --band returns verbatim passages with loc (e.g. docs/mesh.md:L10-L13), the sha of the bytes read, and a confidence band (none, weak, partial, grounded). - Freshness verdicts: each citation is labeled current, stale, as-ingested, cached, or unverified, so you know whether the quoted text still matches what was indexed; --audit shows every document examined. - Receipts and verification: --receipt emits a re-runnable in-toto record, and fux verify receipt.json --rerun --json reports reproduced, drifted:config, drifted:corpus, or unverifiable without ever fetching. - Use Case: Ask "how do we roll back the gateway" and get the exact current lines from the runbook with a sha and freshness verdict, save the receipt, and re-verify it in CI weeks later to confirm nothing drifted. ## Quick Start Ask the assistant to answer your question from the docs with citations by running fux answer with --json and --band, then report each passage with its own locator and freshness verdict.

Frequently Asked Questions about fux-answer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get an answer with exact line citations from my docs?▼

Run fux answer "<question>" --json --band. It ranks documents like fux ask, reads the top three from their sources, and returns verbatim passages with loc line ranges, the sha of the bytes read, and a confidence band.

How do I check whether a cited answer is still current?▼

Run fux answer with --audit and read the freshness verdicts: current, stale, as-ingested, cached, or unverified. A stale verdict means the source changed since indexing, so quote it as the current text and note the index is behind.

How do I verify a fux answer receipt later?▼

Save the answer with --receipt, then run fux verify receipt.json --rerun --json. It re-ranks from the committed index without fetching and reports reproduced, drifted:config, drifted:corpus, or unverifiable. Without --rerun the best verdict is unverifiable.

Does fux answer work offline or without fetching sources?▼

File documents are read from the working tree with no network. Pass --no-refer to answer from the index's titles and headings only, or set fetch_at_answer = false so as-ingested verdicts come from bytes kept at ingest time.

Why does fux answer reject --top or -q flags?▼

fux answer has no --top, no -q, and no --why flags; passing one is a usage error with exit code 2. The number of candidate documents is fixed at three and is not configurable.

What are the limitations of fux verify receipts?▼

fux verify never fetches, so a receipt from a source: refer answer is unverifiable with --rerun. Upgrading fux makes older receipts drifted:config, and editing a cited local file shows as drifted:corpus.