capture-knowledgelisted

# Capture Knowledge ## Purpose Turn something learned or built in this conversation into a durable, generalized note in an external, git-tracked knowledge-base repository ("second brain"), without leaking anything proprietary or personal into it. ## When to use - User says "capture knowledge", "update knowledge base", "update notes", "update second brain", "save this to my notes", "remember this for later", together with a target repository path. - Never trigger this automatically at the end of a task. This is a deliberate, user-initiated action, not a silent background capture, judging what's "worth remembering" is exactly the step that needs a human in the loop. ## 1. Resolve the target repository Use the path the user gave in their request. If no path was given, ask for one, don't guess or default to a repository mentioned earlier in the conversation for an unrelated reason. ```bash test -d "<path>/.git" || echo "not a git repository" ``` If it's not a git repository, stop and ask. ## 2. Check for pre-existing uncommitted changes ```bash git -C "<path>" status --short ``` If the working tree already has unstaged or untracked changes unrelated to this task, leave them alone entirely. Never `git add` a file you didn't write to, even partially, an existing modified file may contain the user's own in-progress work, or something sensitive that has nothing to do with this capture. Stage only the files this skill creates or intentionally edits. ## 3. Learn that reposi