Check
flowchart LR
ask([project]) --> locate --> diagnose
diagnose --> inplace([what is in place])
inplace -.->|"measurement off"| stopped([stopped])
inplace -.->|"not a git repository"| stopped
inplace --> answer([four claims])
Actions
Run the flow above. Read only the next action file.
| Action | Does |
|---|---|
| locate | confirm the CLI |
| diagnose | run it, and present every line it printed |
Transversal rules
- Checking that a hook fired is not the same as checking that a file exists. A run file with only
session_startis not evidence of anything closed. - Run only
aidd telemetry check. Never a script, and never a command belonging to another skill. - Present every printed line. A line this skill leaves out is a claim the user cannot check.
- What is in place is printed first and is never a claim — it appears whether or not measurement is on, and names the file behind every fact so the user can go and change it.
ok,FAILand--are three different answers.--means there was nothing to evaluate, not that the chain is healthy.- A declaration that the recorder is set up is not proof it fired. Relay it as what it is — a fact about configuration, never a promise about behaviour.
- The
aiddcommand cannot be found: say so and check nothing.