Investigate · Asagiri CLI
Investigation locale structurée
CLI path: asa investigate
When to use
Orchestration commands coordinate higher-order Asagiri workloads such as ingestion, syncing, backlog triage, investigative passes, hydrated context payloads, coarse estimates, and workspace-specific automation.
Original CLI synopsis: Investigation locale structurée
Usage
asa investigate [flags]Options
| Flag | Scope | Default | Description |
|---|---|---|---|
--depth | Local | standard | Profondeur: quick|standard|deep|ci |
--dry-run | Inherited | false | Simuler les exécutions sans lancer d'agent ni commandes externes |
--estimate-only | Local | false | Estimation sans rapport complet |
--flow | Local | (empty) | Flow produit |
--from-failed-tests | Local | false | Cibler les tests en échec |
--max-duration | Local | 0 | Durée max (minutes) |
--max-files | Local | 0 | Nombre max de fichiers dans le context pack |
--no-cloud | Local | false | Investigation 100% locale |
--output | Local | markdown | Sortie: markdown|json |
--run | Local | (empty) | ID de run |
--task | Local | (empty) | ID de tâche |
Examples
asa investigateWire richer samples through cobra.Command.Example when the happy path warrants copy/paste-friendly automation beyond this scaffold.
What happens internally
- Hydrates contextual services resolved from $PWD, coordinating git-bound automation, ingestion pipelines, syncing, backlog triage, investigations, MCP hooks, contextual hydration, coarse estimates, and similar orchestrations for this subtree.
Failure modes
- Cobra rejects unknown flags or arity mismatches before any repository side effects occur.
- Asagiri cannot resolve scaffolding when the command is invoked outside an initialised checkout.
- Downstream automation may fail whenever credentials, network endpoints, or cached prerequisites drift from expectations.