From autology
Orchestrates knowledge workflow after commits, pushes, PRs, or decisions: triages context, syncs existing docs, captures new items with topology hints to keep docs accurate.
How this skill is triggered — by the user, by Claude, or both
Slash command
/autology:autology-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Route to the right autology skill after significant actions. Knowledge captured close to the action is more accurate and complete — this workflow keeps docs/ in sync with what actually happened.
Route to the right autology skill after significant actions. Knowledge captured close to the action is more accurate and complete — this workflow keeps docs/ in sync with what actually happened.
/autology:triage-knowledge — context triage: analyze action, return classified list + topology hints/autology:sync-knowledge (use topology hints to verify connected nodes too)/autology:capture-knowledge (use suggested relations from hints to add wikilinks)If triage returns only new items (no existing matches), skip sync — capture runs alone. If triage returns only existing items (nothing new), skip capture — sync runs alone.
Signals for "action completed":
autology-workflow just completed (skip — do not re-trigger):
Action → triage → sync (existing) + capture (new) → done
| Mistake | Fix |
|---|---|
| sync/capture without triage first | Without triage + hints, risk duplicates or missing nodes |
| Ignore topology hints in sync/capture | Use connected/suggested relations to strengthen wikilinks |
| Only capture when user says "remember" | Self-discovered conventions are also capture targets |
npx claudepluginhub curt-park/autology --plugin autologyCaptures decisions, conventions, patterns, issues, and concepts from conversations into docs/ markdown nodes using triage output. Auto-activates on save intents or decision signals.
Captures project-level learnings, conventions, and decisions into memory, rules, or ADR files. Useful when surfacing durable conventions and technical decisions during work.
Curates durable knowledge from delivery cycles, refactors, and reviews into canonical repository memory docs like module cards, contracts, decisions, runbooks, and lessons. Updates existing docs first.