| name | resolve-doc-source |
| argument-hint | [library-or-url] |
| description | Use when adding a documentation source to the dq doc pipeline or asking the best way to ingest a library or site's docs - e.g. 'add docs for X', 'what's the right recipe for <docs-url>', 'resolve doc source'. Resolves the optimal ingest strategy by measurement and adds the recipe to config/doc_sets.toml. |
| context | fork |
| agent | doc-source-resolver |
| metadata | [{"name":"dq ingest pipeline","description":"Resolves the optimal dq-ingest recipe for a doc source by measurement and writes the validated [[sets.ingest]] block to config/doc_sets.toml."},{"name":"dq-ingest","description":"The ingest CLI (url / git / pkg / local) plus the normalize / validate / quality gates the resolution runs."},{"author":"magic-man"},{"tags":["docs","ingest","recipe","resolve"]}] |
Resolve Doc Source
Add this documentation source to the dq doc pipeline: $ARGUMENTS
Resolve the optimal ingest recipe for it - decide by measurement (sample-ingest
each candidate, compare coverage and stub-ratio), apply the validated
[[sets.ingest]] block to config/doc_sets.toml, and return the JSON report.
The resolution methodology and the exact JSON output shape are in your agent
system prompt. If no source was given above, return {"error": "no source provided"}.
Once it finishes, the caller runs make refresh to ingest and index the new set.
References
- references/recipes.md - the
[[sets.ingest]] shape, the four ingest kinds, url_style, and the base_url rule
- references/resolution.md - finding candidates, the sample-ingest + audit rubric, the lessons
- references/quality-gates.md - normalize, validate, quality, refresh, and the apply sequence
- examples/recipes.md - a concrete recipe block per kind (url / git / pkg / local)
- examples/commands.md - candidate discovery, sample-ingest, gate, refresh sequences
