Diagnose your own agent sessions

Start only when the user names mo-debug. A request to debug code, to explain a failure or to review a session in general does not activate it, and no other skill calls it.

Read Обратная связь о методологии completely: friction you hit goes to the user in your answer, and this skill writes no Issue.

What you may read

Take from the user explicit session paths or ids — a Claude session UUID or a Codex thread id — and a bound: --since <ISO-8601>, --max-records <n> or both. Ask for them when they are missing; never search for sessions yourself, and never open a session log with any other tool. Only the bundled helper reads them: