Help us improve
Share bugs, ideas, or general feedback.
From autology
Captures decisions, conventions, patterns, issues, and concepts from conversations into docs/ markdown nodes using triage output. Auto-activates on save intents or decision signals.
npx claudepluginhub curt-park/autology --plugin autologyHow this skill is triggered — by the user, by Claude, or both
Slash command
/autology:capture-knowledgeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Capture knowledge from conversation context into docs/ as markdown nodes. Save immediately — asking confirmation interrupts flow and discourages capture.
Capture knowledge — solutions, context docs, learnings, and principles. Use after fixing non-trivial bugs, creating context for AI, or discovering patterns worth preserving. Triggers: compound, document solution, capture fix, save solution, knowledge compound, document this, save this fix, context, create context, update context, build context, learn, save learning, remember this.
Orchestrates knowledge workflow after commits, pushes, PRs, or decisions: triages context, syncs existing docs, captures new items with topology hints to keep docs accurate.
Share bugs, ideas, or general feedback.
Capture knowledge from conversation context into docs/ as markdown nodes. Save immediately — asking confirmation interrupts flow and discourages capture.
Precondition: if triage has not run this session, run /autology:triage-knowledge first.
Capture the items triage classified as new (→ capture):
When NOT to capture:
| Type | Signals |
|---|---|
| decision | "chose", "decided", "selected", "adopted" |
| component | "created", "built", "implemented", new service/module |
| convention | "always", "never", "must", "should", "the rule is" |
| concept | lifecycle, workflow, domain model, process |
| pattern | reusable approach, strategy, pattern |
| issue | bug, technical debt, bottleneck, known problem |
| session | work session summary, "finished", "completed" |
type = primary classification (what kind?); tags = cross-cutting topics (what about?).
Use triage's new items list as the capture scope:
New items from triage (→ capture):
- [item description] — no matching node
Suggested relations: [[foo]], [[bar]] (shared tags: architecture)
- [item description] — no matching node
Suggested relations: none
Not every triage item needs its own file. Before creating, ask: does this item have enough standalone substance to be useful on its own, or is it a detail of something larger?
type: decision node, not a footnote in the component doc.The deciding criterion is not length but kind: a choice made with rationale → own node; a behavioral detail of an implementation → fold. When folding, capture the detail in the parent node's body. This keeps the graph navigable — thin stub nodes add noise without adding reach.
For each new item that warrants its own node, create docs/{title-slug}.md:
---
title: "Human Readable Title"
type: decision
tags: [tag1, tag2]
---
File naming: docs/{title-slug}.md — lowercase, hyphens, no special characters.
Use triage's suggested relations for wikilinks:
[[title-slug]] wikilink in the new node's body text (wikilink target = filename without .md extension)[[title-slug]] wikilink> **Autology** — Captured [type]: docs/{slug}.md
> Tags: [tags] | Relations: [related nodes if any]
| Mistake | Fix |
|---|---|
| Running capture without triage output | Triage classifies new vs existing — run it first. |
| Capturing items triage classified as existing | Those go to sync, not capture. |
| Ask user for confirmation before saving | Save immediately, then report. |
| Add wikilink only to new node | Also add reverse link to related node. |