Example map¶
The repository ships workflows, named commands, and a TypeScript extension. Use a task guide to run an example, then inspect its source to adapt it.
| Example | Run it | Understand it | Source |
|---|---|---|---|
| Feedback triage | Triage feedback | Annotation before synthesis | triage.yaml |
| Repository context | Prepare a harness handoff | Retaining source evidence | context.yaml |
| Reusable brief | Build it step by step | Compression and reuse | command, flow |
| Failing CI investigation | Investigate failing CI | Evidence boundaries | command, flow |
| date-fns contribution brief | Prepare a contribution brief | Pinned provenance | command, flow |
| Squirrel Census field report | Analyze open data | Snapshot provenance | flow, normalizer |
| GitHub PR evidence | Build an extension | Extension trust | read-only extension |
The native archive includes examples/ and fixtures/. npm installs the command and its runtime support; get the examples from a source checkout when using npm.
Semantic examples require configured profiles. local-small and stronger are names you create, not bundled models. Start with model setup.
Packaged recipe tests check composition, routes, and evidence boundaries with controlled model responses. Live model evidence reports the separate model runs and their limits.