Loading...
Loading...
Found 78 Skills
Двусторонняя сверка кода и графа — уборочный такт: всюду ли код соответствует графу, а граф — коду; конец каждой сущностной задачи. Триггеры: reconcile, «сверь код с графом», «приведи граф в порядок», «протки свою область», «отдай долги графа», does the graph match the code, tidy the graph. Также: задача, записанная крией; феномен-ярлык состояния; комментарий-портянка, пересказывающая граф. Distinct from weaving (ремонт графа изнутри), integrity (claim-аудит), reality-audit (поведенческие заявки). Композирует entry, writing, weaving. Нужны тулы iskron_*.
Ingest a codebase into memory as code pages connected by wiki links. Walks the tree, classifies each code file by role, applies a role template, and writes a code page per meaningful unit under <wiki root>/code/. Resumable: skips files already ingested and current. Not for prose documents; use /loam::adding-to-memory for those.
Write and review shellscript documentation with shdoc annotations. Use when a coding agent creates, edits, or reviews `.sh` files or shell executables and should add, repair, or normalize `@file`, `@brief`, `@description`, `@arg`, `@option`, and `@example` comments to match shdoc conventions.
Write meaningful documentation that explains why not what; focus on complex business logic and self-documenting code
Use when you have a spec or requirements for a multi-step task, before touching code
Call use_skill as your FIRST and ONLY action when the user asks to document, add descriptions to, annotate, or add doc:description attributes to Mule XML files, flows, components, or connectors. Do not read project files first — this skill provides instructions for when to read files. Covers documenting all Mule elements in src/main/mule including flows, sub-flows, configs, listeners, processors, transforms, error handlers, and connectors. When you call use_skill, it must be the only tool call in that response.